1 |
Am Freitag, den 15.05.2009, 23:30 +0300 schrieb Petteri Räty: |
2 |
> William Hubbs wrote: |
3 |
> > On Fri, May 15, 2009 at 03:49:51AM -0700, Robin H. Johnson wrote: |
4 |
> >> On Fri, May 15, 2009 at 10:47:24AM +0200, Tiziano M?ller wrote: |
5 |
> >>> Thanks Robin for finally pushing this in the tree, just didn't find the |
6 |
> >>> time to. |
7 |
> >>> |
8 |
> >>> Maybe it's a good time to emphasize this: Keep in mind that changing the |
9 |
> >>> EAPI in an ebuild requires a revision bump (including reset to unstable |
10 |
> >>> keywords, etc.). |
11 |
> >> That's going to cause a large problem. |
12 |
> > |
13 |
> >> The entire point is that the STABLE ebuilds need to be changed, |
14 |
> >> otherwise they will try to depend on the libusb-1 series (and fail |
15 |
> >> dismally). |
16 |
> > |
17 |
> >> For switching from EAPI0 to EAPI1, if the ebuild still compiles fine, |
18 |
> >> then I see no reason that a slot dep change cannot be just put in with |
19 |
> >> the EAPI change. (The same cannot be said for EAPIx -> EAPI2, as further |
20 |
> >> changes are needed for that case). |
21 |
> > |
22 |
> > As far as I know, the only time you need to do a rev bump and reset to |
23 |
> > unstable is if you change the files that are installed by the package. |
24 |
> > |
25 |
> > So, as far as I know, unless you are migrating to an EAPI that is not |
26 |
> > stable or changing the files that are installed by the package, it is |
27 |
> > not necessary to do a rev bump just for changing the EAPI as long as |
28 |
> > you make sure that the ebuild emerges fine under the new EAPI. |
29 |
> > |
30 |
> |
31 |
> Indeed there's no problem switching EAPIs as long as a stable Portage |
32 |
> supports the EAPI you are migrating to. Portage was buggy with this when |
33 |
> EAPI 2 was introduced but that has since been fixed. |
34 |
|
35 |
Wrong. For example: |
36 |
- stuff like docompress may change the content being installed depending |
37 |
on the package manager |
38 |
- --disable-static (maybe in a later EAPI) changes content |
39 |
- slot-dep-operators change the rdepend of installed packages, so it |
40 |
changes how the package manager has to handle reverse packages on |
41 |
uninstall (in EAPI 3) |
42 |
|
43 |
On the other hand you also have to make sure you have a stable portage |
44 |
for a time long enough so mostly everyone has it installed. Otherwise |
45 |
you could break users systems pretty badly depending on the packages. |
46 |
And Arch-Teams usually do a pretty good job in catching such cases. |
47 |
|
48 |
And we also always said that a rev bump should be done on non trivial |
49 |
changes or non-build-fixes and changing the EAPI is technical seen |
50 |
mostly a non-trivial change. |
51 |
|
52 |
Do we want to document the following? (do we have already?) |
53 |
- When is it allowed to use an EAPI in the tree (given as offset to the |
54 |
release of portage supporting that eapi) |
55 |
- When is it allowed to use an EAPI in the stable tree (given as offset |
56 |
of when a portage version supporting that EAPI got stable) |
57 |
|
58 |
Cheers, |
59 |
Tiziano |
60 |
|
61 |
|
62 |
-- |
63 |
Tiziano Müller |
64 |
Gentoo Linux Developer, Council Member |
65 |
Areas of responsibility: |
66 |
Samba, PostgreSQL, CPP, Python, sysadmin, GLEP Editor |
67 |
E-Mail : dev-zero@g.o |
68 |
GnuPG FP : F327 283A E769 2E36 18D5 4DE2 1B05 6A63 AE9C 1E30 |