public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christoph Mende <angelos@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: Reinstating eclasses
Date: Tue, 4 Nov 2008 20:23:53 +0100	[thread overview]
Message-ID: <20081104202353.43c68d49@gentoo.org> (raw)
In-Reply-To: <20081104131525.6821d0ed@halo.dirtyepic.sk.ca>

[-- Attachment #1: Type: text/plain, Size: 996 bytes --]

On Tue, 4 Nov 2008 13:15:25 -0600
Ryan Hill <dirtyepic@gentoo.org> wrote:

> On Tue, 04 Nov 2008 13:43:55 -0500
> Joe Peterson <lavajoe@gentoo.org> wrote:
> 
> > Christoph Mende wrote:
> > > Now the most logical name for an eclass like that
> > > would be xfce4.eclass, except that eclass already exists.
> > 
> > Since the new eclass is not version specific, how about simply
> > "xfce.eclass"?

Well, the desktop is usually called Xfce4, plus that'd match gnome2...
and more or less kde4

> why bother introducing yet another xfce*.eclass when you can re-use an
> existing one?
> 
That's what I want to do :P
We currently have xfce4.eclass, xfce42.eclass and xfce44.eclass. 42 and
44 are obviously versioned, 4 isn't, but isn't nearly compatible with
my new one, partly because it was used (and probably exclusively
written) for 4.2.

-- 
Christoph Mende
Gentoo/AMD64 Operational Lead and Release Engineering
GPG: EE2A 454A 6A3B A2D8 E43B  FF45 2A19 C3B3 6DA0 C1AF

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2008-11-04 19:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04 16:43 [gentoo-dev] Reinstating eclasses Christoph Mende
2008-11-04 17:35 ` Zac Medico
2008-11-04 18:22   ` Petteri Räty
2008-11-04 18:30     ` Joe Peterson
2008-11-04 18:43 ` Joe Peterson
2008-11-04 19:15   ` [gentoo-dev] " Ryan Hill
2008-11-04 19:19     ` Joe Peterson
2008-11-04 19:23     ` Christoph Mende [this message]
2008-11-04 19:30       ` Joe Peterson
2008-11-04 23:30         ` Duncan
2008-11-05 16:19           ` Steve Long

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=20081104202353.43c68d49@gentoo.org \
    --to=angelos@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