1 |
AllenJB <gentoo-lists@××××××××××.uk> writes: |
2 |
|
3 |
> First of all, a tip: If a portage upgrade is available, do "emerge |
4 |
> portage" first. New versions of portage often have new or improved |
5 |
> features - in this case portage 2.1.6 includes, among other things, |
6 |
> the ability to automatically handle most blockers. |
7 |
|
8 |
Though even the portage2.2 pre-releases do not handle all the cases that |
9 |
should be able to be handled automatically. An example is one which |
10 |
encountered yesterday - foo-x-y-z was already installed and foo-x-y+1-0 |
11 |
was available for update. There are already installed packages which |
12 |
have (R)DEPEND="=foo-x.y*" and others with (R)DEPEND=">=foo-x.0.0". So |
13 |
the already installed foo-x.y.z satisfies all the depends, but the new |
14 |
foo-x.y+1.0 does not. Yet 'emerge -auDv world' flagged a conflict of |
15 |
trying to install two versions of an unslotted package - when the |
16 |
'obvious' resolution would be keep the already installed version and not |
17 |
upgrade rather than requiring the user to manually mask the new |
18 |
version. Not only is this less work for the user, but it would also |
19 |
allow the automatic upgrade if and when the packages with the specific |
20 |
dependency on the lower version were changed to allow the newer one |
21 |
without the user having to track the blocking ebuilds to see when the |
22 |
(R)DEPENDs change and then manually remove the mask. |