В Втр, 24/06/2008 в 01:53 +0200, Robert Buchholz пишет:
> 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.
But do we allow KEYWORDS in eclasses? Why? Each package should be tested
inde
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"
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
