1 |
On Tue, 11 Oct 2005 19:52:47 +0200 Nikodemus Karlsson |
2 |
<nikodemus@×××××××××.se> wrote: |
3 |
> tisdag 11 oktober 2005 19.35 skrev Douglas James Dunn: |
4 |
> > Can you paste a emerge "-uDpvt" world please? |
5 |
> |
6 |
> Here we go... |
7 |
> Calculating world dependencies ...done! |
8 |
> [blocks B ] <mail-client/pine-4.64-r1 (is blocking |
9 |
> [ebuild U ] mail-client/pine-4.64-r1 [4.63-r3] -debug -kerberos |
10 |
> -largeterminal -ldap +pam -passfile +ssl 3,202 kB |
11 |
> [ebuild N ] net-mail/uw-mailutils-2004g 2,194 kB |
12 |
|
13 |
Nothing wrong with that. The new version of pine depends on |
14 |
uw-mailutils-2004g. The first line tells you that pine versions _prior_ |
15 |
to 4.64-r1 do not work with uw-mailutils-2004g. That means you have to |
16 |
unmerge pine and then emerge it again. It will install the new pine |
17 |
and pull uw-mailutils as a dependency. You would think, portage could |
18 |
have been a bit smarter and do that itself, but it is dangerous. What |
19 |
if you need pine while emerge is still running and it unmerges it while |
20 |
you are using it? |
21 |
|
22 |
> almost every time when I do a complete packages upgrade using emerge |
23 |
> -u world, portage flags for new packages which is going to be |
24 |
> installed. Is there an option to get rid of this behavior, so I only |
25 |
> get the updated packages with one command? |
26 |
|
27 |
Why would you want to do that? If the package, that you want to upgrade, |
28 |
depends on something you don't have installed it will obviously have to |
29 |
emerge it first. There is only one situation where it is not the case. |
30 |
The new package may be a dependency based on a (new) USE-flag. If it is |
31 |
so you can disable that USE-flag in package.keywords and not install |
32 |
the new package. |
33 |
|
34 |
|
35 |
Cheers, |
36 |
Renat |
37 |
|
38 |
-- |
39 |
Probleme kann man niemals mit derselben Denkweise loesen, |
40 |
durch die sie entstanden sind. |
41 |
(Einstein) |