From: David Leverton <levertond@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Major changes to the Gnome2 Eclasses
Date: Fri, 14 Mar 2008 12:26:42 +0000 [thread overview]
Message-ID: <200803141226.42842.levertond@googlemail.com> (raw)
In-Reply-To: <47DA6C2F.2040403@gentoo.org>
On Friday 14 March 2008 12:14:39 Petteri Räty wrote:
> David Leverton kirjoitti:
> > Maybe worth adding a dummy to the current version of the eclass so that
> > ebuilds can be updated now, instead of suddenly all at once as soon as
> > the new eclass is committed?
>
> And break a bunch of ebuilds to stable users. No thanks.
Hmm? I don't see how this would break anything... unless you mean that
exporting the dummy function would overwrite one that actually does something
important, but that's easily worked around by not exporting it until the
ebuilds are fixed, as far as I can tell. In any case, not doing anything
until the new eclass is committed is going to break ebuilds until they're
updated to call the new function, whether stable or ~arch.
--
gentoo-dev@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-03-14 12:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 7:14 [gentoo-dev] [RFC] Major changes to the Gnome2 Eclasses Rémi Cardona
2008-03-14 9:09 ` Denis Dupeyron
2008-03-14 10:21 ` Rémi Cardona
2008-03-14 11:34 ` Denis Dupeyron
2008-03-14 11:52 ` David Leverton
2008-03-14 12:14 ` Petteri Räty
2008-03-14 12:26 ` David Leverton [this message]
2008-03-14 12:56 ` Petteri Räty
2008-03-14 12:20 ` Rémi Cardona
2008-03-14 12:58 ` David Leverton
2008-03-14 12:22 ` Petteri Räty
2008-03-17 16:32 ` Rémi Cardona
2008-03-17 17:51 ` Nirbheek Chauhan
2008-03-17 19:57 ` Rémi Cardona
2008-03-17 23:42 ` Gilles Dartiguelongue
2008-03-18 1:06 ` Bo Ørsted Andresen
2008-03-18 6:43 ` Rémi Cardona
2008-03-18 7:06 ` Dawid Węgliński
2008-03-18 0:35 ` Petteri Räty
2008-03-18 6:37 ` Rémi Cardona
2008-03-18 11:33 ` Petteri Räty
2008-03-20 8:23 ` [gentoo-dev] " 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=200803141226.42842.levertond@googlemail.com \
--to=levertond@googlemail.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