On Sunday 04 December 2005 20:47, Ned Ludd wrote:
> that sounds like it would solve the problems ferringb has
> pointed out in the past.
That works fine, a part an "Eclass blabla inherited illegally" errors on
unmerge of older ebuilds.
The main problem is that what was proposed for shadow deps req
On Sun, 2005-12-04 at 20:14 +0100, Luca Barbato wrote:
> Ned Ludd wrote:
> >
> > You should talk to ferringb about why it's evil to remove functions from
> > an eclass ever.
> >
>
> eclasses can't inherit from other eclasses?
>
> Just splitting functionality on another eclass and keep the forme
Ned Ludd wrote:
You should talk to ferringb about why it's evil to remove functions from
an eclass ever.
eclasses can't inherit from other eclasses?
Just splitting functionality on another eclass and keep the former
eclass providing everything by inheriting the new one doesn't work?
lu
-
On Sun, 2005-12-04 at 08:26 -0600, Jory A. Pratt wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I have found a restrictions in out mozconfig-2 eclass. Splitting the
> eclass core configuration out to a seprate eclass will fix the
> restrictions. I have placed the eclasses at
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have found a restrictions in out mozconfig-2 eclass. Splitting the
eclass core configuration out to a seprate eclass will fix the
restrictions. I have placed the eclasses at
http://dev.gentoo.org/~anarchy/eclass for view. With the new mozcore
