1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On 2009.06.10 22:21, Tobias Scherbaum wrote: |
5 |
[snip] |
6 |
|
7 |
> The main "problem" is that there is no deployment process for newer |
8 |
> EAPIs specified right now. In the past we had something like "there |
9 |
> must be two releases (stage sets) including a Portage version |
10 |
> supporting new features" before people were allowed to use new |
11 |
> features in tree. We had a timeframe of something about a half year |
12 |
> between introduction of new features and usage of them. At least in |
13 |
> theory. |
14 |
> |
15 |
> While having such a longer timeframe would make the deployment of new |
16 |
> EAPIs somewhat easier (especially the special cases when newer |
17 |
> versions of a package were migrated to a shiny new EAPI which isn't |
18 |
> supported by a stable Portage yet and there's a need for quick |
19 |
> versions bump due to security bugs) I think something inbetween that |
20 |
> old process and the |
21 |
> currently used one would be useful. For example something like: New |
22 |
> EAPIs can be used in tree once a Portage version supporting that |
23 |
> specific EPAI has been marked as stable plus a transition period of - |
24 |
> say - 4 weeks after the Portage version has been made stable on the |
25 |
> first architecture. |
26 |
|
27 |
What about the case where the new EAPI breaks backwards compatibility |
28 |
with existing package managers, as would be the case with glep 55? |
29 |
|
30 |
Its quite true that such changes can be introduced after a wait and |
31 |
only upset late adoptors. By implementing the key feature of glep 55, |
32 |
which is making the EAPI known to the PM without sourcing the ebuild, |
33 |
we would only need one last wait to introduce new features in this |
34 |
way in later EAPIs.PMs would then know the EAPI in advance and ignore |
35 |
ebuilds using EAPIs they don't understand. |
36 |
|
37 |
[snip] |
38 |
|
39 |
> |
40 |
> Tobias |
41 |
> |
42 |
> |
43 |
|
44 |
- -- |
45 |
Regards, |
46 |
|
47 |
Roy Bamford |
48 |
(NeddySeagoon) a member of |
49 |
gentoo-ops |
50 |
forum-mods |
51 |
treecleaners |
52 |
trustees |
53 |
-----BEGIN PGP SIGNATURE----- |
54 |
Version: GnuPG v2.0.11 (GNU/Linux) |
55 |
|
56 |
iEYEARECAAYFAkowMGEACgkQTE4/y7nJvaswcgCfUa5dKLY8YYMyL7FjhIcNVXJg |
57 |
pO8An33Z2+1lm2jzkh9ciANzOhH+PqXv |
58 |
=yiKg |
59 |
-----END PGP SIGNATURE----- |