On Thu, Feb 19, 2009 at 11:09:30PM +0530, Arun Raghavan wrote:
> > On the git->rsync gateway:
> > For non-distfiles:
> > 1. Extract SHA1 from Git 
> > 2. Compare to actual file (Git does this implicitly, esp if you have
> >    signed Git commits, but you can check again if you want).
> > 3. Generate SHA256/RMD160/other.
> > 4. Append the full hash to Manifest.
> So how would this work for the developers themselves?
> 
> Do we use a separate Manifest.dist which would be used to generate the
> server Manifest (and could be used locally to)? This would be one extra,
> barely-used disk block per package leading to a >50 MB blow-up in the
> sync tree size (more for the git tree, but that, I presume, is not a
> problem).
The 'Manifest' file committed by developers contains ONLY 'DIST'
entries. Every git action you do on your local tree would detect other
changes.

-- 
Robin Hugh Johnson
Gentoo Linux Developer & Infra Guy
E-Mail     : robbat2@g.o
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85