On Tue, Jun 24, 2008 at 01:53:55AM +0200, Robert Buchholz wrote: > Hi, > > I've stumbled upon an inconsitency between package managers the other > day [1], which was due to both an ebuild and an eclass defining > inconsisting KEYWORDS. > > bla-1.ebuild: > inherit myeclass > KEYWORDS="~arch" > > myeclass.eclass: > KEYWORDS="arch" > > Portage will resolve this by overwriting the variable, so the last > (~arch) wins. Paludis, on the other hand, merges the variables, so it > is KEYWORDS="~arch arch". > > The PMS draft [2] defines that "IUSE, DEPEND, RDEPEND and PDEPEND" > variables be merged when defined in both eclass and ebuild (Section > 7.2), but only says "May be defined in an eclass" about KEYWORDS > (Section 8.2). > > Anyone up to toss a coin whose bug it is, and maybe we can have a more > specific wording in the PMS?
Paludis bug; if you want KEYWORDS incremental, it'll need to be in >=eapi2, too nasty of a change to shoehorn into existing (in use) eapis. Cheers, ~harring
pgpGcmR0UL61B.pgp
Description: PGP signature
