1 |
Hi Michael, |
2 |
|
3 |
On 23-03-2011 10:39:27 +0100, Michael Seifert wrote: |
4 |
> On the first glance, the rough specifications and tasks seem pretty |
5 |
> straight forward: |
6 |
> 1. Create a tool that extracts an ebuild descriptor from an existing |
7 |
> ebuild (containing arch, version, dependencies, ebuild location,...) |
8 |
> 2. Make portage work with the ebuild descriptors at first, then fetching |
9 |
> the required files |
10 |
> 3. Create a tool that assembles an ebuild with its patches, sources, and |
11 |
> eclasses |
12 |
> 4. Make portage use the assembled archives |
13 |
|
14 |
Can you quantify the gains here? How much space do you win by removing |
15 |
the build-recipe code? Could you also do with the metadata directory |
16 |
alone? How much do you lose to fetch the ebuilds you need eventually? |
17 |
Do you intend to cache "full" ebuilds? |
18 |
|
19 |
In short: |
20 |
What do you win, when and how? |
21 |
|
22 |
:) |
23 |
|
24 |
Regards, |
25 |
|
26 |
-- |
27 |
Fabian Groffen |
28 |
Gentoo on a different level |