Date: Sun, 11 Sep 2011 23:09:45 -0700 From: perryh@pluto.rain.com To: lev@freebsd.org Cc: FreeBSD-Ports@freebsd.org Subject: Re: [RFC] New ports idea: github / gitorious / bitbucket direct support. Message-ID: <4e6da229.3XVC%2Bd3Qo7pQcAni%perryh@pluto.rain.com> In-Reply-To: <99834116.20110911130131@serebryakov.spb.ru> 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> <99834116.20110911130131@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Lev Serebryakov <lev@freebsd.org> wrote: > ... 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) = 7b7c763a9d1d4edca7b5b415ab297fec > MD5 (test2.tar.gz) = 703ac5387b2bd1146434516f1d761ed9 > % gzip -d test1.tar.gz test2.tar.gz > % md5 test1.tar test2.tar > MD5 (test1.tar) = 0ba33aa8ff6bffeeeb2d96efc38eec85 > MD5 (test2.tar) = 0ba33aa8ff6bffeeeb2d96efc38eec85 That is arguably a bug in "tar czf" :) but it is easy enough to work around; we just need a checksum method -- e.g. SHA256_UNGZ -- that pipes the distfile through gunzip when computing its checksum.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4e6da229.3XVC%2Bd3Qo7pQcAni%perryh>