From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j3Q0o2HY028089 for ; Tue, 26 Apr 2005 00:50:03 GMT Received: from adsl-67-39-48-198.dsl.milwwi.ameritech.net ([67.39.48.198] helo=exodus) by smtp.gentoo.org with esmtpa (Exim 4.43) id 1DQEH5-0005XG-RJ for gentoo-dev@lists.gentoo.org; Tue, 26 Apr 2005 00:50:03 +0000 Date: Mon, 25 Apr 2005 19:50:28 -0500 From: Brian Harring To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Per-category and per-package eclasses Message-ID: <20050426005028.GB29554@exodus.wit.org> References: <200504251343.52450@zippy.emcb.local> <46059ce10504250608421915ff@mail.gmail.com> <426CE220.40409@gentoo.org> <20050425144703.5fb0233e@snowdrop> <20050426024928.20e1570f@sven.genone.homeip.net> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050426024928.20e1570f@sven.genone.homeip.net> User-Agent: Mutt/1.5.8i X-Archives-Salt: 32ef443f-6c85-47b5-a973-74e20447334b X-Archives-Hash: 1e6408a7be35e6ebb9ae6235100aa9f9 On Tue, Apr 26, 2005 at 02:49:28AM +0200, Marius Mauch wrote: > On Mon, 25 Apr 2005 14:47:03 +0100 > Ciaran McCreesh wrote: > > > On Mon, 25 Apr 2005 15:27:12 +0300 Marius Mauch > > 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