From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Reinstating eclasses
Date: Tue, 04 Nov 2008 20:22:01 +0200 [thread overview]
Message-ID: <491092C9.5080301@gentoo.org> (raw)
In-Reply-To: <491087C6.9030309@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]
Zac Medico wrote:
> Christoph Mende wrote:
>> Hi,
>
>> I'm currently working on a new eclass for Xfce4 that, as opposed to the
>> previous ones (xfce42.eclass, xfce44.eclass), is supposed to be used
>> for all versions. Now the most logical name for an eclass like that
>> would be xfce4.eclass, except that eclass already exists. It seems like
>> it was used for Xfce 4.2 and has been deprecated for quite some time
>> now. Obviously, packages using that eclass (which is zero in the main
>> tree and zero in the xfce herd's overlay btw) wouldn't work with my new
>> eclass, so I can't just extend said eclass. Now my big question is: Do
>> I have to think of a new name for my eclass (was thinking of something
>> like xfce4-r1.eclass, which I don't really like though) or can I just
>> overwrite the old eclass?
>
>
> Considering that stable portage (2.1.4.4) uses environment.bz2 and
> doesn't need the eclasses to exist for uninstall or binary packages,
> and it's exceedingly unlikely that it will hurt anyone, I think you
> should go ahead and overwrite the old eclass.
>
The names of eclasses aren't shown to users and I think figuring out a
new name is a minor inconvenience so I would just go with the safe route.
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2008-11-04 18:22 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 [this message]
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
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=491092C9.5080301@gentoo.org \
--to=betelgeuse@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