Re: [gentoo-dev] Paludis and Profiles

[Brian Harring <ferringb@gmail.com>]

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

On Tue, May 16, 2006 at 03:56:38PM -0700, Brian Harring wrote:
> If your parent parsing implementation handled N parents on a single 
> line (rather then parent per line as you do now), portage would 
> explode rather then silently use the left most.  Your implementation 
> isn't doing that however...

And that won't even work.  Woot.  About the only guranteed "portage 
will choke and not invalidly use N parent profiles if it doesn't 
support it are"-
1) specify the parents prefixed with #, fex
# ..
# ../blah
End result is that python will throw a TypeError (might be 
ValueError).  Not incredibly clean.
2) insane profile inheritance version trick.  Require the 
leftmost parent to point at a custom profile, say profiles/version1, 
which has a nice little bashrc along the lines of 
die "upgade your $PKG_MANAGER- your current version cannot parse this 
profile properly".
If the package manager knows of version1, it just filters that parent 
out as it goes- if it doesn't, any/all ebuild actions result in a 
forced bail as soon as control is transfered over to ebuild env.

Both solutions suck, and the alternatives of "just ignore it" or 
"require left parsed profile to be minimally sane" don't cut it all 
that well.

~harring

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