public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Georgi Georgiev <chutz@gg3.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Per-category and per-package eclasses
Date: Mon, 25 Apr 2005 22:35:13 +0900	[thread overview]
Message-ID: <20050425133513.GB100634@lion.gg3.net> (raw)
In-Reply-To: <426CE220.40409@gentoo.org>

maillog: 25/04/2005-15:27:12(+0300): Marius Mauch types
> 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.

Plus, imagine how much stuff will break when you move a package to a new
category.

-- 
*>   Georgi Georgiev   *> Never underestimate the power of human       *>
<*    chutz@gg3.net    <* stupidity.                                   <*
*>  +81(90)2877-8845   *>                                              *>
-- 
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2005-04-25 13:35 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 [this message]
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=20050425133513.GB100634@lion.gg3.net \
    --to=chutz@gg3.net \
    --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