| 1 |
On 07/05/2010 08:55 PM, Pacho Ramos wrote: |
| 2 |
> El lun, 05-07-2010 a las 19:38 +0200, Harald van Dijk escribió: |
| 3 |
>> On Mon, Jul 05, 2010 at 07:01:27PM +0200, Arfrever Frehtes Taifersar Arahesis wrote: |
| 4 |
>>> 2010-07-05 18:36:09 Tomáš Chvátal napisał(a): |
| 5 |
>>>> Dne 5.7.2010 18:34, Arfrever Frehtes Taifersar Arahesis napsal(a): |
| 6 |
>>>>> python.eclass uses colors for build time outputting, which doesn't communicate anything for users. |
| 7 |
>>>>> |
| 8 |
>>>> + echo " ${_RED}*${_NORMAL} ${_RED}Deprecation Warning: NEED_PYTHON |
| 9 |
>>>> variable is deprecated and will be banned on 2010-10-01.${_NORMAL}" |
| 10 |
>>>> + echo " ${_RED}*${_NORMAL} ${_RED}Use PYTHON_DEPEND variable instead of |
| 11 |
>>>> NEED_PYTHON variable.${_NORMAL}" |
| 12 |
>>>> + echo " ${_RED}*${_NORMAL} ${_RED}The ebuild needs to be fixed. Please |
| 13 |
>>>> report a bug, if it has not been already reported.${_NORMAL}" |
| 14 |
>>>> |
| 15 |
>>>> The above is build outputting since when? |
| 16 |
>>> |
| 17 |
>>> The colored, non-logged output in deprecation warnings is used as exception to increase |
| 18 |
>>> the chance that ebuild maintainers will be notified earlier about the necessity of changes |
| 19 |
>>> in given ebuilds. |
| 20 |
>> |
| 21 |
>> einfo/ewarn/eerror output is repeated by default when emerge exits. By |
| 22 |
>> not using einfo/ewarn/eerror, you are making it less likely that others |
| 23 |
>> will be reading your deprecation notices. |
| 24 |
>> |
| 25 |
> |
| 26 |
> I fully agree with this, I think that using ewarn would be much more |
| 27 |
> useful for all of us |
| 28 |
|
| 29 |
We should not be spamming our users with deprecation notices. ewarn is |
| 30 |
for messages that users should take action for. People can for example |
| 31 |
have configured to receive email on these messages. |
| 32 |
|
| 33 |
Regards, |
| 34 |
Petteri |
Archives