| 1 |
On Wed, 2006-05-17 at 20:55 +0100, Ciaran McCreesh wrote: |
| 2 |
> The plan, which may be full of holes, may change and may just be me |
| 3 |
> being crazy, is to replace using a stage with something like: |
| 4 |
|
| 5 |
OK. So not only are you planning on replacing portage, you're planning |
| 6 |
on replacing Release Engineering. Thanks, but we are not interested. |
| 7 |
|
| 8 |
> paludis --config-suffix install --install system |
| 9 |
> |
| 10 |
> which will then go off and grab the relevant binary packages from a |
| 11 |
> remote location and merge them onto ROOT. Being able to do something |
| 12 |
> along these lines is a) one of several reasons for --config-suffix and |
| 13 |
> b) a large part of why I don't want to use the Portage tbz2 format, |
| 14 |
> where metadata and contents aren't separated. |
| 15 |
|
| 16 |
Remote location, huh? What about non-networked installations? |
| 17 |
|
| 18 |
> | > | #2. Can paludis build all of the release materials required by the |
| 19 |
> | > | Release Engineering release guidelines? |
| 20 |
> | > |
| 21 |
> | > No. Nor will it ever, nor will it need to. |
| 22 |
> | |
| 23 |
> | Will you then instead try to create new guidelines that do result |
| 24 |
> | into development of releases? |
| 25 |
> |
| 26 |
> Assuming the above ends up not being insane, then yes. |
| 27 |
|
| 28 |
Which would have to be accepted by the Release Engineering project. |
| 29 |
Perhaps this point has been lost on you up until now. |
| 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 |
You mean like *all* of the GRP-handling code? |
| 48 |
|
| 49 |
-- |
| 50 |
Chris Gianelloni |
| 51 |
Release Engineering - Strategic Lead |
| 52 |
x86 Architecture Team |
| 53 |
Games - Developer |
| 54 |
Gentoo Linux |
Archives