Grant, Apologies; I can't find your note from yesterday, so I can't respond to the correct topic. One question just occurred to me; if it's been addressed before, apologies about that, too. Your requirement that any alternative package manager support any ebuild which portage supports seems essential, except for a boundary case. What about ebuilds which for whatever reason are invalid (serious specification violation, for example, to the extent that QA would reject them), but portage accepts them anyway. Must the alternative accept them as well? In a case like this, it seems to me that the ebuild works because of a bug in portage, and there should be no complaint if as a side effect of fixing this bug the ebuild in question quit working. If memory serves me, things like this have indeed happened. I can't recall a specific, however.
Regards, Ferris -- Ferris McCormick (P44646, MI) <[EMAIL PROTECTED]> Developer, Gentoo Linux (Devrel, Sparc)
signature.asc
Description: This is a digitally signed message part
