1 |
On Wed, 17 May 2006 21:30:13 +0200 Paul de Vrieze <pauldv@g.o> |
2 |
wrote: |
3 |
| > | #1. Can paludis work with catalyst? |
4 |
| > |
5 |
| > No. Nor will it ever, nor will it need to. |
6 |
| |
7 |
| Am I correct in reading this like you will implement a catalyst |
8 |
| replacement? |
9 |
|
10 |
The plan, which may be full of holes, may change and may just be me |
11 |
being crazy, is to replace using a stage with something like: |
12 |
|
13 |
paludis --config-suffix install --install system |
14 |
|
15 |
which will then go off and grab the relevant binary packages from a |
16 |
remote location and merge them onto ROOT. Being able to do something |
17 |
along these lines is a) one of several reasons for --config-suffix and |
18 |
b) a large part of why I don't want to use the Portage tbz2 format, |
19 |
where metadata and contents aren't separated. |
20 |
|
21 |
| > | #2. Can paludis build all of the release materials required by the |
22 |
| > | Release Engineering release guidelines? |
23 |
| > |
24 |
| > No. Nor will it ever, nor will it need to. |
25 |
| |
26 |
| Will you then instead try to create new guidelines that do result |
27 |
| into development of releases? |
28 |
|
29 |
Assuming the above ends up not being insane, then yes. |
30 |
|
31 |
| > | #3. Can paludis build a portage-compatible VDB that can be used |
32 |
| > | by the Gentoo Linux Installer? |
33 |
| > |
34 |
| > No. Nor will it ever, nor will it need to. |
35 |
| |
36 |
| Why will it not need to? Usage and support of paludis would be a lot |
37 |
| greater it it could work (with limited feature perhaps) on a portage |
38 |
| compatible VDB. You might work with the portage team to have portage |
39 |
| be aware of extensions in the VDB and handle them smartly (ignore |
40 |
| them?). At that point paludis could offer extra features while being |
41 |
| still portage compatible. |
42 |
|
43 |
I'm pretty sure it would be easier to just not use anything in the |
44 |
installer that relies upon VDB when using Paludis. The installer code |
45 |
is flexible enough to make this not tooooo tricky. |
46 |
|
47 |
-- |
48 |
Ciaran McCreesh |
49 |
Mail : ciaran dot mccreesh at blueyonder.co.uk |
50 |
|
51 |
|
52 |
-- |
53 |
gentoo-dev@g.o mailing list |