1 |
On Sat, Sep 17, 2011 at 10:26:57PM -0700, Zac Medico wrote: |
2 |
> On 09/17/2011 08:47 PM, Donnie Berkholz wrote: |
3 |
> > On 14:06 Fri 16 Sep , Zac Medico wrote: |
4 |
> >> Bumping the EAPI of the root profiles/eapi file would be a different |
5 |
> >> matter, since it applies to the whole repository. If you want to |
6 |
> >> version bump that repository-level EAPI, then you need to wait until |
7 |
> >> at least 6 months after supporting package managers have been |
8 |
> >> available in stable. |
9 |
> > |
10 |
> > So in your opinion, it would be fine to bump profiles/eapi to EAPI=4 |
11 |
> > now? |
12 |
> |
13 |
> Yes, it's feasible. As a consequence, we may get some complaints from |
14 |
> users who haven't upgraded during the last six months. |
15 |
|
16 |
|
17 |
Bit more than complaints; any system running a PM older than 6 months |
18 |
or so (regardless of paludis/portage/pkgcore) will have to roll their |
19 |
own profile to merge *anything*. |
20 |
|
21 |
Period. |
22 |
|
23 |
A pkg going to an unsupported eapi precludes the package from being |
24 |
used; bumping the root profile node to 4 (or any node in the users |
25 |
chain) means they /cannot use that profile/. |
26 |
|
27 |
|
28 |
If people are seriously going to pull something this level of |
29 |
heinous, at the very least plan it- it's a sizable enough breakage |
30 |
other things could/should be shoved in (including giving people |
31 |
significant warning). |
32 |
|
33 |
|
34 |
To be absolutely clear, You bump the base to EAPI4, you're actively |
35 |
making every system w/ a 6 month lag basically invalidated. |
36 |
|
37 |
For reference of the actual eapi usage in the tree (pinspect |
38 |
eapi_usage), is the following: |
39 |
|
40 |
eapi: '0' 10629 pkgs found, 36.73% of the repository |
41 |
eapi: '2' 7254 pkgs found, 25.07% of the repository |
42 |
eapi: '3' 5315 pkgs found, 18.37% of the repository |
43 |
eapi: '4' 5013 pkgs found, 17.32% of the repository |
44 |
eapi: '1' 728 pkgs found, 2.52% of the repository |
45 |
|
46 |
|
47 |
> For users like |
48 |
> these, we could take a snapshot of the tree before the EAPI is bumped, |
49 |
> and archive it so they can use it to update their package manager to a |
50 |
> version that supports the new EAPI. |
51 |
|
52 |
Target the profiles; no need to snapshot the whole tree unless the |
53 |
plan is to bump 83% of the tree forward to EAPI4 shortly there |
54 |
after (which is mildly rediculous in it's own anyways)... |
55 |
|
56 |
~harring |