| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On Fri, May 15, 2009 at 03:49:51AM -0700, Robin H. Johnson wrote: |
| 5 |
> On Fri, May 15, 2009 at 10:47:24AM +0200, Tiziano M?ller wrote: |
| 6 |
> > Thanks Robin for finally pushing this in the tree, just didn't find the |
| 7 |
> > time to. |
| 8 |
> > |
| 9 |
> > Maybe it's a good time to emphasize this: Keep in mind that changing the |
| 10 |
> > EAPI in an ebuild requires a revision bump (including reset to unstable |
| 11 |
> > keywords, etc.). |
| 12 |
> That's going to cause a large problem. |
| 13 |
> |
| 14 |
> The entire point is that the STABLE ebuilds need to be changed, |
| 15 |
> otherwise they will try to depend on the libusb-1 series (and fail |
| 16 |
> dismally). |
| 17 |
> |
| 18 |
> For switching from EAPI0 to EAPI1, if the ebuild still compiles fine, |
| 19 |
> then I see no reason that a slot dep change cannot be just put in with |
| 20 |
> the EAPI change. (The same cannot be said for EAPIx -> EAPI2, as further |
| 21 |
> changes are needed for that case). |
| 22 |
|
| 23 |
As far as I know, the only time you need to do a rev bump and reset to |
| 24 |
unstable is if you change the files that are installed by the package. |
| 25 |
|
| 26 |
So, as far as I know, unless you are migrating to an EAPI that is not |
| 27 |
stable or changing the files that are installed by the package, it is |
| 28 |
not necessary to do a rev bump just for changing the EAPI as long as |
| 29 |
you make sure that the ebuild emerges fine under the new EAPI. |
| 30 |
|
| 31 |
- -- |
| 32 |
William Hubbs |
| 33 |
gentoo accessibility team lead |
| 34 |
williamh@g.o |
| 35 |
-----BEGIN PGP SIGNATURE----- |
| 36 |
Version: GnuPG v2.0.11 (GNU/Linux) |
| 37 |
|
| 38 |
iEYEARECAAYFAkoNgNcACgkQblQW9DDEZTgorACdGfiXec4JUIC3UJDL/sGctbEi |
| 39 |
FpwAn3UxUOjxuQUxl0w5S95M271+306Q |
| 40 |
=jinO |
| 41 |
-----END PGP SIGNATURE----- |
Archives