1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Hello Gentoo team, |
5 |
|
6 |
the other SoC ideas of interest are projects #14 [1] and #25 [2]. |
7 |
The idea is to automatically create ebuild descriptors that contain |
8 |
metadata only. This way, server load on emerge --sync will be reduced, |
9 |
since the ebuilds will only be fetched, if the package is about to be |
10 |
installed. |
11 |
In my opinion, this is the first step to take before trying to implement |
12 |
the self-contained ebuilds. I think of them as Python eggs that contain |
13 |
everything you need for installation (ebuild, patches, eclasses, sources). |
14 |
Are these packaged ebuilds meant to be a replacement for the current |
15 |
ebuilds in the long term? If so, the above mentioned reduction of server |
16 |
load and network traffic would be diminished. Say you want to install 5 |
17 |
packages that use the eutils.eclass, you will have to download it 5 |
18 |
times (in a compressed archive of course). |
19 |
|
20 |
A tool for creating the packaged ebuilds does not seem to cause much |
21 |
trouble, either. What seems a bit more difficult to me, though, are the |
22 |
changes to portage. |
23 |
|
24 |
On the first glance, the rough specifications and tasks seem pretty |
25 |
straight forward: |
26 |
1. Create a tool that extracts an ebuild descriptor from an existing |
27 |
ebuild (containing arch, version, dependencies, ebuild location,...) |
28 |
2. Make portage work with the ebuild descriptors at first, then fetching |
29 |
the required files |
30 |
3. Create a tool that assembles an ebuild with its patches, sources, and |
31 |
eclasses |
32 |
4. Make portage use the assembled archives |
33 |
|
34 |
However, since I have merged TWO project ideas, I surely have overlooked |
35 |
some traps :) |
36 |
Probably I underestimated points 2 and 4? |
37 |
Please, share you opinions. |
38 |
|
39 |
[1] http://www.gentoo.org/proj/en/userrel/soc/ideas.xml#doc_chap2_sect14 |
40 |
[2] http://www.gentoo.org/proj/en/userrel/soc/ideas.xml#doc_chap2_sect25 |
41 |
|
42 |
|
43 |
Best regards and thanks in advance |
44 |
Michael Seifert |
45 |
-----BEGIN PGP SIGNATURE----- |
46 |
Version: GnuPG v2.0.17 (GNU/Linux) |
47 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
48 |
|
49 |
iEYEARECAAYFAk2Jv88ACgkQnzX+Jf4GTUyj3wCgxijF5HzPswow4gsqqABnBGuT |
50 |
jsYAmwcj4wI1LznnwCnpWfGWXEKO0Ji9 |
51 |
=nW4G |
52 |
-----END PGP SIGNATURE----- |