| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
kartik rustagi wrote: |
| 5 |
> Hi, I am interested in working for Gentoo as a student in this years |
| 6 |
> Gsoc. After looking at Gentoo's idea page I am interested in working |
| 7 |
> for the "Cache sync" suggested by Zac Medico. |
| 8 |
|
| 9 |
First off, I'm not sure who posted this on the wiki, but it wasn't |
| 10 |
me. Being the portage project lead, I get listed as the contact for |
| 11 |
anything involving portage internals. |
| 12 |
|
| 13 |
The "Cache sync" idea is certainly a useful one. In portage-2.1.6 |
| 14 |
already have support for something similar, but it's for binary |
| 15 |
packages rather than unbuilt ebuilds. All that you have to do is |
| 16 |
share $PKGDIR via http or ftp and clients configure PORTAGE_BINHOST |
| 17 |
in make.conf to download packages when emerge's --getbinpkg option |
| 18 |
is specified. |
| 19 |
|
| 20 |
Doing the same kind of thing with unbuilt ebuilds may seem |
| 21 |
appealing, but it will be a lot of work that will have very little |
| 22 |
payoff when you consider that the entire tree of ebuilds can fit |
| 23 |
into a 45Mb squashfs filesystem. The 600Mb value mentioned in the |
| 24 |
wiki is really a worst-case that's brought about by file system |
| 25 |
limitations such as lack of transparent compression and the |
| 26 |
inability to pack multiple small files into a single block of |
| 27 |
storage space. |
| 28 |
|
| 29 |
> I guess implementation |
| 30 |
> of this idea will take care of another interesting idea listed on the |
| 31 |
> idea wiki as "Tree-wide collision checking and provided files |
| 32 |
> database" to a certain extent. |
| 33 |
|
| 34 |
The collision checking thing makes more sense in terms of binary |
| 35 |
packages, since the installed file list of an ebuild is unknown |
| 36 |
until after it has been built. One way that this could be |
| 37 |
implemented would be to create a tool that harvests file contents |
| 38 |
data from a repository of binary packages and uploads it to a |
| 39 |
central server. |
| 40 |
- -- |
| 41 |
Thanks, |
| 42 |
Zac |
| 43 |
-----BEGIN PGP SIGNATURE----- |
| 44 |
Version: GnuPG v2.0.10 (GNU/Linux) |
| 45 |
|
| 46 |
iEYEARECAAYFAkm4KMcACgkQ/ejvha5XGaM0/gCfaLWGiM0InG56lPjhqs0xxFNu |
| 47 |
ZIAAoNcMVlp0byKatIClichnXa5jD3UC |
| 48 |
=Xkes |
| 49 |
-----END PGP SIGNATURE----- |
Archives