Re: [gentoo-dev] Paludis and Profiles

[Brian Harring <ferringb@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 2563 bytes --]

On Thu, May 18, 2006 at 09:58:02PM +0100, Ciaran McCreesh wrote:
> On Thu, 18 May 2006 22:39:20 +0200 Paul de Vrieze <pauldv@gentoo.org>
> | > | What he is driving it at is that either paludis is an alternative
> | > | (yet on disk compatible) primary, or it's a secondary- you keep
> | > | debating the compatibility angle, thus the logical conclussion is
> | > | that it's a secondary.
> | >
> | > We're an alternative, not entirely on disc compatible primary.
> | 
> | This means that you could choose to meet the requirements that I am
> | currently writing down in GLEP shape for package managers that desire
> | to replace portage as the primary package manager. Those requirements
> | can be met, but would limit the freedom choise of implementation of
> | the package manager.
> 
> GLEPs are to *Enhance*, not to hold back.

Several of your gleps restrict the tree (rhetoric not withstanding)- 
this is fundamentally no different, it's a restriction on what the is 
required of a pkg manager for it to be a primary available in the 
tree- this includes whatever profiles/mods it requires/wants.


> | > Design choice. We chose not to continue with previous design
> | > mistakes that exist only because of limitations in Portage's dep
> | > resolver where we can do so without requiring ebuild changes.
> | 
> | This is a valid design choise. It does however mean that paludis
> | perhaps can not meet the requirements for being a replacement for
> | portage as gentoo primary package manager.
> 
> You could come up with a requirement saying that "any replacement for
> Portage must have an 'o' in its name". Wouldn't make it a valid
> requirement. Fact is, Paludis can be used as and is being used as a
> primary package manager.

No one is disputing that.  What they are disputing is whether paludis 
has any place in the tree if it's not going to be ondisk (whether 
profile, ebuild, or vdb) compatible with portage.

Say paludis *did* get into the tree, and the changes you've coded into 
paludis already took hold- we would have a tree that is part paludis, 
and part portage.

If it's not going to be compatible under guidelines council/approved 
glep dictates, then it has no place in the tree.

Aside from that, lay off the smart ass "any replacement for portage 
must have an 'o' in its name" crap- folks aren't going to budge on 
this one, so just address the points they're raising rather then 
dodging it (thus requiring another email from 'em dragging the answer 
out of you).

~harring

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]