public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dan Meltzer <parallelgrapefruit@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Per-category and per-package eclasses
Date: Mon, 25 Apr 2005 09:08:18 -0400	[thread overview]
Message-ID: <46059ce10504250608421915ff@mail.gmail.com> (raw)
In-Reply-To: <200504251343.52450@zippy.emcb.local>

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?

On 4/25/05, Elfyn McBratney <beu@gentoo.org> 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 ? :)
> 
> Best,
> Elfyn
> 
> --
> Elfyn McBratney                                     http://beu.merseine.nu/
> beu/irc.freenode.net                            http://dev.gentoo.org/~beu/
> +------------O.o--------------------- http://dev.gentoo.org/~beu/pubkey.asc
> 
> PGP Key ID: 0x69DF17AD
> PGP Key Fingerprint:
>   DBD3 B756 ED58 B1B4 47B9  B3BD 8D41 E597 69DF 17AD
> 
> 
>

-- 
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2005-04-25 13:08 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 [this message]
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
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=46059ce10504250608421915ff@mail.gmail.com \
    --to=parallelgrapefruit@gmail.com \
    --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