1 |
On Thu, Feb 19, 2009 at 11:09:30PM +0530, Arun Raghavan wrote: |
2 |
> > On the git->rsync gateway: |
3 |
> > For non-distfiles: |
4 |
> > 1. Extract SHA1 from Git |
5 |
> > 2. Compare to actual file (Git does this implicitly, esp if you have |
6 |
> > signed Git commits, but you can check again if you want). |
7 |
> > 3. Generate SHA256/RMD160/other. |
8 |
> > 4. Append the full hash to Manifest. |
9 |
> So how would this work for the developers themselves? |
10 |
> |
11 |
> Do we use a separate Manifest.dist which would be used to generate the |
12 |
> server Manifest (and could be used locally to)? This would be one extra, |
13 |
> barely-used disk block per package leading to a >50 MB blow-up in the |
14 |
> sync tree size (more for the git tree, but that, I presume, is not a |
15 |
> problem). |
16 |
The 'Manifest' file committed by developers contains ONLY 'DIST' |
17 |
entries. Every git action you do on your local tree would detect other |
18 |
changes. |
19 |
|
20 |
-- |
21 |
Robin Hugh Johnson |
22 |
Gentoo Linux Developer & Infra Guy |
23 |
E-Mail : robbat2@g.o |
24 |
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 |