atom feed24 messages in org.freebsd.freebsd-portsRe: [RFC] New ports idea: github / gi...
FromSent OnAttachments
Lev SerebryakovSep 9, 2011 3:30 am 
Baptiste DaroussinSep 9, 2011 6:04 am 
Lev SerebryakovSep 9, 2011 6:12 am 
Klaus T. AehligSep 9, 2011 6:24 am 
Klaus T. AehligSep 9, 2011 6:54 am 
Lev SerebryakovSep 9, 2011 6:57 am 
Klaus T. AehligSep 9, 2011 7:05 am 
Baptiste DaroussinSep 9, 2011 7:28 am 
Shaun AmottSep 9, 2011 8:26 am 
Klaus T. AehligSep 9, 2011 8:38 am 
per...@pluto.rain.comSep 10, 2011 12:11 am 
Matthew D. FullerSep 10, 2011 12:15 am 
Lev SerebryakovSep 10, 2011 1:50 am 
Shaun AmottSep 10, 2011 9:04 am 
Chris ReesSep 10, 2011 10:33 am 
Ruslan MahmatkhanovSep 10, 2011 10:47 am 
Chris ReesSep 10, 2011 10:57 am 
Ruslan MahmatkhanovSep 10, 2011 11:09 am 
Klaus T. AehligSep 10, 2011 11:37 am 
per...@pluto.rain.comSep 10, 2011 4:14 pm 
Lev SerebryakovSep 11, 2011 2:01 am 
Peter PentchevSep 11, 2011 2:26 pm 
per...@pluto.rain.comSep 11, 2011 4:14 pm 
b. f.Sep 11, 2011 7:01 pm 
Subject:Re: [RFC] New ports idea: github / gitorious / bitbucket direct support.
From:per...@pluto.rain.com (per@pluto.rain.com)
Date:Sep 10, 2011 4:14:36 pm
List:org.freebsd.freebsd-ports

"Matthew D. Fuller" <full@over-yonder.net> wrote:

On Sat, Sep 10, 2011 at 07:03:41AM -0700 I heard the voice of per@pluto.rain.com, and lo! it spake thus:

If I am understanding correctly, you seem to be saying that two distfiles autogenerated from the _same_ tag etc. in the _same_ repository, and actually containing exactly the same code, can nevertheless generate different checksums!? Wouldn't that be a bug in the DVCS?

There're all sorts of ways the same content could wind up with different checksums. The compression may happen slightly differently, higher, or lower. The files could wind up in the tarball in a different order. Timestamps could differ. etc.

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:

* The compression method, and the ordering of the files, should be consistent.

* Each file's timestamp in the tarball should be the selected version's timestamp as recorded in the repository, typically the time when the selected version of that file was committed to the VCS. Ditto for directories, provided the VCS maintains directory history.

* If the VCS does _not_ maintain directory history (which is a deficiency, but not really a "bug"), each directory's timestamp in the tarball should match the most-recent file or subdirectory in that directory.