1 |
William Hubbs wrote: |
2 |
> On Fri, May 15, 2009 at 03:49:51AM -0700, Robin H. Johnson wrote: |
3 |
>> On Fri, May 15, 2009 at 10:47:24AM +0200, Tiziano M?ller wrote: |
4 |
>>> Thanks Robin for finally pushing this in the tree, just didn't find the |
5 |
>>> time to. |
6 |
>>> |
7 |
>>> Maybe it's a good time to emphasize this: Keep in mind that changing the |
8 |
>>> EAPI in an ebuild requires a revision bump (including reset to unstable |
9 |
>>> keywords, etc.). |
10 |
>> That's going to cause a large problem. |
11 |
> |
12 |
>> The entire point is that the STABLE ebuilds need to be changed, |
13 |
>> otherwise they will try to depend on the libusb-1 series (and fail |
14 |
>> dismally). |
15 |
> |
16 |
>> For switching from EAPI0 to EAPI1, if the ebuild still compiles fine, |
17 |
>> then I see no reason that a slot dep change cannot be just put in with |
18 |
>> the EAPI change. (The same cannot be said for EAPIx -> EAPI2, as further |
19 |
>> changes are needed for that case). |
20 |
> |
21 |
> As far as I know, the only time you need to do a rev bump and reset to |
22 |
> unstable is if you change the files that are installed by the package. |
23 |
> |
24 |
> So, as far as I know, unless you are migrating to an EAPI that is not |
25 |
> stable or changing the files that are installed by the package, it is |
26 |
> not necessary to do a rev bump just for changing the EAPI as long as |
27 |
> you make sure that the ebuild emerges fine under the new EAPI. |
28 |
> |
29 |
|
30 |
Indeed there's no problem switching EAPIs as long as a stable Portage |
31 |
supports the EAPI you are migrating to. Portage was buggy with this when |
32 |
EAPI 2 was introduced but that has since been fixed. |
33 |
|
34 |
Regards, |
35 |
Petteri |