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 usWe 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
signature.asc
Description: OpenPGP digital signature
