William Hubbs wrote:
> On Fri, May 15, 2009 at 03:49:51AM -0700, Robin H. Johnson wrote:
>> On Fri, May 15, 2009 at 10:47:24AM +0200, Tiziano M?ller wrote:
>>> Thanks Robin for finally pushing this in the tree, just didn't find the
>>> time to.
>>>
>>> Maybe it's a good time to emphasize this: Keep in mind that changing the
>>> EAPI in an ebuild requires a revision bump (including reset to unstable
>>> keywords, etc.).
>> That's going to cause a large problem.
> 
>> The entire point is that the STABLE ebuilds need to be changed,
>> otherwise they will try to depend on the libusb-1 series (and fail
>> dismally).
> 
>> For switching from EAPI0 to EAPI1, if the ebuild still compiles fine,
>> then I see no reason that a slot dep change cannot be just put in with
>> the EAPI change. (The same cannot be said for EAPIx -> EAPI2, as further
>> changes are needed for that case).
>  
>  As far as I know, the only time you need to do a rev bump and reset to
>  unstable is if you change the files that are installed by the package.
> 
>  So, as far as I know, unless you are migrating to an EAPI that is not
>  stable or changing the files that are installed by the package, it is
>  not necessary to do a rev bump just for changing the EAPI as long as
>  you make sure that the ebuild emerges fine under the new EAPI.
> 

Indeed there's no problem switching EAPIs as long as a stable Portage
supports the EAPI you are migrating to. Portage was buggy with this when
EAPI 2 was introduced but that has since been fixed.

Regards,
Petteri