public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Aaron Walker <ka0ttic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Per-category and per-package eclasses
Date: Mon, 25 Apr 2005 09:54:27 -0400	[thread overview]
Message-ID: <426CF693.7090109@gentoo.org> (raw)
In-Reply-To: <200504251343.52450@zippy.emcb.local>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Elfyn McBratney wrote:
> Hi folks,
> 
> The other night, some of us in #gentoo-uk got talking about per-category and 
> per-package eclasses, the idea being that each category, and each package, 
> could have it's own 'eclass' subdirectory containing category- or 
> package-local eclasses.  This in addition to having global eclasses in 
> gentoo-x86/eclass.
> 
> For example (totally hypothetical), the php-sapi* eclasses would be a primse 
> example of a category-local eclass (their only used by the PHP SAPI ebuilds).  
> I can't find any eclasses that exist currently that'd be a good example of a 
> local-eclass, but hopefully you get the idea.
> 
> Thoughts ?  Anything I've missed ciaranm ? :)

I like the idea.  cron.eclass would definitely fit in sys-process/eclass/
(although could we move existing eclasses anyways?).

I definitely see an advantage to package local eclasses (any package with a
non-trivial build system).  All non version-specific stuff could be kept there.
- --
Talk sense to a fool and he calls you foolish.
		-- Euripides

Aaron Walker <ka0ttic@gentoo.org>
[ BSD | cron | forensics | shell-tools | commonbox | netmon | vim | web-apps ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCbPaTC3poscuANHARAjmhAJ9duCJNb6DDK6kDL9tFhi/qLhy2BQCgnD6M
wPGaZ6HQp22zGGzVhcZblXs=
=rXCW
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2005-04-25 13:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-25 12:43 [gentoo-dev] Per-category and per-package eclasses Elfyn McBratney
2005-04-25 13:08 ` Dan Meltzer
2005-04-25 12:27   ` Marius Mauch
2005-04-25 13:35     ` Georgi Georgiev
2005-04-25 13:47     ` Ciaran McCreesh
2005-04-26  0:49       ` Marius Mauch
2005-04-26  0:50         ` Brian Harring
2005-04-26  8:54           ` Ciaran McCreesh
2005-04-25 13:54 ` Aaron Walker [this message]
2005-04-25 14:13   ` Ciaran McCreesh
2005-04-25 14:20 ` Mike Frysinger
2005-04-25 14:27   ` Ciaran McCreesh
2005-04-25 14:43     ` Mike Frysinger
2005-04-25 14:33   ` Elfyn McBratney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=426CF693.7090109@gentoo.org \
    --to=ka0ttic@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox