1 |
Roman Zilka (Mon, 4 Jul 2011 23:34:01 +0200): |
2 |
> Neil Bothwick (Mon, 4 Jul 2011 22:16:18 +0100): |
3 |
> > On Mon, 4 Jul 2011 22:48:44 +0200, Roman Zilka wrote: |
4 |
> > |
5 |
> > > Not quite. This is how I'm thinking: if '-ep world' says virtual/pam |
6 |
> > > needs to be installed, then it either |
7 |
> > > * is in the world file, or |
8 |
> > > * is in the system set, or |
9 |
> > > * is a buildtime or runtime dependency (immediate or deep) of one of the |
10 |
> > > packages in the world set (i.e., world file and system set combined). |
11 |
> > |
12 |
> > There's another possibility, that it is one of a number of packages that |
13 |
> > satisfy a particular dependency, the first listed one. If you have |
14 |
> > another package installed that fulfils this dependency, emerge -u world |
15 |
> > won't need to do anything, but with emerge -e world you are telling |
16 |
> > portage that the other package is not installed, so it picks the first |
17 |
> > dependency from the list. |
18 |
> |
19 |
> I checked that - in this case, there are no alternatives. |
20 |
|
21 |
Ah, I see. I'm sorry, I wasn't thinking enough. Yeah, virtual/pam may |
22 |
be one of a list. But if nothing else, I have openssh and openssh says: |
23 |
RDEPEND="pam? ( virtual/pam ) |
24 |
No alternatives there. And I don't have virtual/pam, but do have |
25 |
openssh. So why does '-uDN world' not pull virtual/pam in? |
26 |
|
27 |
-rz |