From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Deprecation of python_version(), python_mod_exists(), python_tkinter_exists(), distutils_python_version() and distutils_python_tkinter() in EAPI <=2
Date: Thu, 4 Mar 2010 21:19:59 -0600 [thread overview]
Message-ID: <20100304211959.6b5f3f28@gentoo.org> (raw)
In-Reply-To: 19343.32932.875175.8128@a1i15.kph.uni-mainz.de
[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]
On Thu, 4 Mar 2010 10:43:00 +0100
Ulrich Mueller <ulm@gentoo.org> wrote:
> >>>>> On Thu, 04 Mar 2010, Petteri Räty wrote:
>
> >> I think removal of functions is a special case of "Adding and
> >> Updating Eclasses" and we already have a policy for this.
>
> > Removing functions needs a migration plan. For example how long to
> > have a warning there, how long before it can be removed etc.
>
> There may be no general answer to these questions. If it's an eclass
> with limited scope and if the functions are no longer used in the
> tree, then I don't see the need for a long transition period. OTOH,
> for widespread eclasses like eutils you'd probably want it.
>
> > I don't see how you can get those from the common policy?
>
> "If you don't email gentoo-dev first, and end up breaking something,
> expect to be in a lot of trouble."
Now that's a policy I can get behind. :)
--
fonts, by design, by neglect
gcc-porting, for a fact or just for effect
wxwidgets @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-03-05 3:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 18:27 [gentoo-dev] Deprecation of python_version(), python_mod_exists(), python_tkinter_exists(), distutils_python_version() and distutils_python_tkinter() in EAPI <=2 Arfrever Frehtes Taifersar Arahesis
2010-03-03 6:52 ` Petteri Räty
2010-03-03 7:52 ` [gentoo-dev] " Ryan Hill
2010-03-03 8:47 ` Tomáš Chvátal
2010-03-03 9:23 ` Nirbheek Chauhan
2010-03-03 11:09 ` Petteri Räty
2010-03-03 12:40 ` Ryan Hill
2010-03-03 15:55 ` Petteri Räty
2010-03-03 21:39 ` Ryan Hill
2010-03-04 7:13 ` Petteri Räty
2010-03-04 7:39 ` Ulrich Mueller
2010-03-04 7:55 ` Petteri Räty
2010-03-04 9:43 ` Ulrich Mueller
2010-03-05 3:19 ` Ryan Hill [this message]
2010-03-03 12:47 ` Ciaran McCreesh
2010-03-03 15:08 ` Duncan
2010-03-03 15:46 ` Petteri Räty
2010-03-05 9:54 ` [gentoo-dev] " Peter Hjalmarsson
2010-03-05 11:12 ` Petteri Räty
2010-03-05 20:14 ` [gentoo-dev] " Ryan Hill
2010-03-05 21:00 ` Mike Frysinger
2010-03-06 5:42 ` Petteri Räty
2010-03-05 18:40 ` Duncan
2010-03-05 19:16 ` Mike Frysinger
2010-03-03 14:02 ` [gentoo-dev] " Jeremy Olexa
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=20100304211959.6b5f3f28@gentoo.org \
--to=dirtyepic@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