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

[Ciaran McCreesh <ciaranm@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]

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/ .

-- 
Ciaran McCreesh : Gentoo Developer (Vim, Fluxbox, shell tools)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]