From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Per-category and per-package eclasses
Date: Mon, 25 Apr 2005 15:13:24 +0100 [thread overview]
Message-ID: <20050425151324.738619b2@snowdrop> (raw)
In-Reply-To: <426CF693.7090109@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 765 bytes --]
On Mon, 25 Apr 2005 09:54:27 -0400 Aaron Walker <ka0ttic@gentoo.org>
wrote:
| I like the idea. cron.eclass would definitely fit in
| sys-process/eclass/ (although could we move existing eclasses
| anyways?).
Long-term, yes, at least if things are implemented the way I was
thinking when I was talking about it yesterday. Note, however, that I
was mildly intoxicated at the time, so this idea might not actually be a
very smart way of doing things (hence why I made beu write it up -- if
it turns out it's a lousy idea, you can all flame him for being silly
enough to take it seriously).
--
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 --]
next prev parent reply other threads:[~2005-04-25 14:13 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
2005-04-25 14:13 ` Ciaran McCreesh [this message]
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=20050425151324.738619b2@snowdrop \
--to=ciaranm@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