Date: Sun, 11 Sep 2011 13:01:31 +0400 From: Lev Serebryakov <lev@FreeBSD.org> To: perryh@pluto.rain.com Cc: FreeBSD-Ports@freebsd.org Subject: Re: [RFC] New ports idea: github / gitorious / bitbucket direct support. Message-ID: <99834116.20110911130131@serebryakov.spb.ru> In-Reply-To: <4e6c4fc7.M6OsWGol0SLyr/IR%perryh@pluto.rain.com> References: <765103585.20110909143052@serebryakov.spb.ru> <20110909130458.GO31003@azathoth.lan> <4e6b6e3d.58E89hPS0974IMyM%perryh@pluto.rain.com> <20110910071532.GA68847@over-yonder.net> <4e6c4fc7.M6OsWGol0SLyr/IR%perryh@pluto.rain.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Perryh. You wrote 11 =F1=E5=ED=F2=FF=E1=F0=FF 2011 =E3., 10:05:59: > I can't address the non-specific "etc", but I would claim that each > of those 3 specific examples is a VCS bug. Creating a tarball of a > particular content set _should_ be a deterministic process: Once again: gzip, for example, has "timestamp" field in header. Try this locally, without any [D]VCS: % mkdir test && echo "one" > test/one.txt && echo "two" > test/two.txt % tar czf test1.tar.gz test && sleep 5 && tar czf test2.tar.gz test % md5 test1.tar.gz test2.tar.gz MD5 (test1.tar.gz) =3D 7b7c763a9d1d4edca7b5b415ab297fec MD5 (test2.tar.gz) =3D 703ac5387b2bd1146434516f1d761ed9 % gzip -d test1.tar.gz test2.tar.gz % md5 test1.tar test2.tar MD5 (test1.tar) =3D 0ba33aa8ff6bffeeeb2d96efc38eec85 MD5 (test2.tar) =3D 0ba33aa8ff6bffeeeb2d96efc38eec85 % --=20 // Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?99834116.20110911130131>