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] Minor changes in python.eclass and distutils.eclass
Date: Mon, 05 Jul 2010 21:06:02 +0300	[thread overview]
Message-ID: <4C321F0A.2090804@gentoo.org> (raw)
In-Reply-To: <1278352513.14168.66.camel@localhost.localdomain>

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

On 07/05/2010 08:55 PM, Pacho Ramos wrote:
> El lun, 05-07-2010 a las 19:38 +0200, Harald van Dijk escribió:
>> On Mon, Jul 05, 2010 at 07:01:27PM +0200, Arfrever Frehtes Taifersar Arahesis wrote:
>>> 2010-07-05 18:36:09 Tomáš Chvátal napisał(a):
>>>> Dne 5.7.2010 18:34, Arfrever Frehtes Taifersar Arahesis napsal(a):
>>>>> python.eclass uses colors for build time outputting, which doesn't communicate anything for users.
>>>>>
>>>> +	echo " ${_RED}*${_NORMAL} ${_RED}Deprecation Warning: NEED_PYTHON
>>>> variable is deprecated and will be banned on 2010-10-01.${_NORMAL}"
>>>> +	echo " ${_RED}*${_NORMAL} ${_RED}Use PYTHON_DEPEND variable instead of
>>>> NEED_PYTHON variable.${_NORMAL}"
>>>> +	echo " ${_RED}*${_NORMAL} ${_RED}The ebuild needs to be fixed. Please
>>>> report a bug, if it has not been already reported.${_NORMAL}"
>>>>
>>>> The above is build outputting since when?
>>>
>>> The colored, non-logged output in deprecation warnings is used as exception to increase
>>> the chance that ebuild maintainers will be notified earlier about the necessity of changes
>>> in given ebuilds.
>>
>> einfo/ewarn/eerror output is repeated by default when emerge exits. By
>> not using einfo/ewarn/eerror, you are making it less likely that others
>> will be reading your deprecation notices.
>>
> 
> I fully agree with this, I think that using ewarn would be much more
> useful for all of us

We should not be spamming our users with deprecation notices. ewarn is
for messages that users should take action for. People can for example
have configured to receive email on these messages.

Regards,
Petteri


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

  reply	other threads:[~2010-07-05 18:04 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-05 15:23 [gentoo-dev] Minor changes in python.eclass and distutils.eclass Arfrever Frehtes Taifersar Arahesis
2010-07-05 16:13 ` Samuli Suominen
2010-07-05 16:17   ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 16:26     ` Samuli Suominen
2010-07-05 16:34       ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 16:36         ` Tomáš Chvátal
2010-07-05 17:01           ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 17:38             ` Harald van Dijk
2010-07-05 17:43               ` Harald van Dijk
2010-07-05 17:55               ` Pacho Ramos
2010-07-05 18:06                 ` Petteri Räty [this message]
2010-07-05 16:37         ` Ciaran McCreesh
2010-07-05 17:02           ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 18:00         ` Mark Loeser
2010-07-05 18:29           ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 19:18             ` Mark Loeser
2010-07-05 20:23               ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 21:28                 ` Samuli Suominen
2010-07-05 21:38                   ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 21:49                     ` Samuli Suominen
2010-07-05 22:07                       ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 22:29                 ` Mike Frysinger
2010-07-05 23:31                   ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 23:37                     ` Mike Frysinger
2010-07-14 22:36                       ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 18:26 ` Petteri Räty
2010-07-05 19:59   ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 20:18     ` Petteri Räty
2010-07-05 19:37 ` Alex Alexander
2010-07-05 22:50 ` Jorge Manuel B. S. Vicetto
2010-07-05 23:18   ` Jeroen Roovers
2010-07-06  6:33     ` Petteri Räty

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=4C321F0A.2090804@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