public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Deprecation of python_version(), python_mod_exists(), python_tkinter_exists(), distutils_python_version() and distutils_python_tkinter() in EAPI <=2
Date: Sat, 06 Mar 2010 07:42:17 +0200	[thread overview]
Message-ID: <4B91EB39.9060404@gentoo.org> (raw)
In-Reply-To: <20100305141433.2403abc6@gentoo.org>

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

On 03/05/2010 10:14 PM, Ryan Hill wrote:
> 
> Because then people use them.  Don't ask me why.  I have things I deprecated
> over two years ago still being used by a dozen ebuilds bumped within the last
> three months.  You should be familiar with this behaviour wrt.
> built_with_use.  So, when I'm making changes I still have to maintain the
> deprecated stuff.
> 

built_with_use isn't using eerror and it wasn't scanned by repoman so
unless you read the whole ebuild you could miss it when bumping. If we
have devs ignoring eerrors out of the ebuild, then we should rather get
rid of them. It's much harder to spot you are using a deprecated
function when it doesn't exist at all as then the error message during
emerge doesn't stand out in any form.

Regards,
Petteri


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]

  parent reply	other threads:[~2010-03-06  5:43 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
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 [this message]
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=4B91EB39.9060404@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