On 01/18/2010 10:07 AM, Ulrich Mueller wrote:
>>>>>> On Sun, 17 Jan 2010, Petteri Räty wrote:
> 
>> With GLEP 42 and proper logging of e* messages I think we shouldn't
>> annoy users any more with ebeep or epause
> 
> Agreed.
> 
>> so attached is a patch only defines these functions for EAPIs 0, 1
>> and 2. Anyone have a reason to keep these around for EAPI 3?
> 
> We wouldn't gain much by this, because we still have to go through all
> ebuilds using ebeep and epause and change them to EAPI 3.
> 

This would force people to upgrade when migrating to EAPI 3.

> This would be at least the same amount of work as removing the ebeep
> and epause calls from all ebuilds. Why don't we do this instead and
> leave the eclass as it is?
> 

This would make sure no-one uses these even in overlays.

> There are already enough differences between EAPIs for devs to learn,
> and IMHO we shouldn't introduce additional complications such as EAPI
> dependent eclass behaviour (except where necessary, e.g. src_prepare).
> 

Yes but as people shouldn't have the need for these there's not that
much to learn here.

Regards,
Petteri

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to