Re: [gentoo-dev] Per-category and per-package eclasses

[Brian Harring <ferringb@gentoo.org>]

On Tue, Apr 26, 2005 at 02:49:28AM +0200, Marius Mauch wrote:
> On Mon, 25 Apr 2005 14:47:03 +0100
> Ciaran McCreesh <ciaranm@gentoo.org> wrote:
> 
> > On Mon, 25 Apr 2005 15:27:12 +0300 Marius Mauch <genone@gentoo.org>
> > wrote:
> > | Dan Meltzer wrote:
> > | > I can see the use for a category one, but I can see no point for a
> > | > package-local one, if you're going to have it specific for one
> > | > package, why not just put it in the ebuild, and have no eclass at
> > | > all?
> > | 
> > | Actually I'd say the opposite: There is definitely a use for 
> > | package-local eclasses, however I don't see the point for
> > | category-local  eclasses (especially as that would very funny to get
> > | it working). Example for package-local eclasses? Whenever you define
> > | a function in an  ebuild that isn't version specific.
> > 
> > Category-specific: app-vim/eclass/vim-plugin.eclass
> > Package-specific: any package with a non-trivial build system that
> > doesn't change too much between versions.
> > 
> > Making it work is 'easy', just make inherit first try /cat/pkg/eclass/
> > then /cat/eclass/ then finally /eclass/ .
One thing I'm not getting out of this, is why y'all can't just abuse 
the looser grouped layout of eclasses under g33, and implement it 
within that dir...
~brian
-- 
gentoo-dev@gentoo.org mailing list