Re: [gentoo-dev] Paludis and Profiles

[Ciaran McCreesh <ciaran.mccreesh@blueyonder.co.uk>]

On Wed, 17 May 2006 21:30:13 +0200 Paul de Vrieze <pauldv@gentoo.org>
wrote:
| > | #1. Can paludis work with catalyst?
| >
| > No. Nor will it ever, nor will it need to.
| 
| Am I correct in reading this like you will implement a catalyst
| replacement?

The plan, which may be full of holes, may change and may just be me
being crazy, is to replace using a stage with something like:

paludis --config-suffix install --install system

which will then go off and grab the relevant binary packages from a
remote location and merge them onto ROOT. Being able to do something
along these lines is a) one of several reasons for --config-suffix and
b) a large part of why I don't want to use the Portage tbz2 format,
where metadata and contents aren't separated.

| > | #2. Can paludis build all of the release materials required by the
| > | Release Engineering release guidelines?
| >
| > No. Nor will it ever, nor will it need to.
| 
| Will you then instead try to create new guidelines that do result
| into development of releases?

Assuming the above ends up not being insane, then yes.

| > | #3. Can paludis build a portage-compatible VDB that can be used
| > | by the Gentoo Linux Installer?
| >
| > No. Nor will it ever, nor will it need to.
| 
| Why will it not need to? Usage and support of paludis would be a lot
| greater it it could work (with limited feature perhaps) on a portage
| compatible VDB. You might work with the portage team to have portage
| be aware of extensions in the VDB and handle them smartly (ignore
| them?). At that point paludis could offer extra features while being
| still portage compatible.

I'm pretty sure it would be easier to just not use anything in the
installer that relies upon VDB when using Paludis. The installer code
is flexible enough to make this not tooooo tricky.

-- 
Ciaran McCreesh
Mail            : ciaran dot mccreesh at blueyonder.co.uk


-- 
gentoo-dev@gentoo.org mailing list