| 1 |
Greg Turner posted on Mon, 07 Jul 2014 03:14:14 -0700 as excerpted: |
| 2 |
|
| 3 |
> WTF is up with it? Why does it love the first Atom so much more than |
| 4 |
> the others? |
| 5 |
> |
| 6 |
> It could be such a useful feature, but, in practice, it just never seems |
| 7 |
> to do what I want it to. Is it a bug? |
| 8 |
|
| 9 |
[FWIW, the HTML isn't particularly appreciated.] |
| 10 |
|
| 11 |
AFAIK, the first atom is simply the one chosen to fill the dependency if |
| 12 |
none of the || choices are currently installed. As such the first one is |
| 13 |
the default, but if one of the others is installed that should fill the |
| 14 |
dependency just as well. |
| 15 |
|
| 16 |
As well, I /believe/ (but don't know for sure) that the resolver prefers |
| 17 |
other slots of installed packages to those not installed at all, so a new |
| 18 |
slot of something already installed but not in the first/default position |
| 19 |
should be preferred over the first/default dependency. Obviously this |
| 20 |
would be particularly important for subslot dependencies. |
| 21 |
|
| 22 |
Is that not the behavior you're seeing? |
| 23 |
|
| 24 |
-- |
| 25 |
Duncan - List replies preferred. No HTML msgs. |
| 26 |
"Every nonfree program has a lord, a master -- |
| 27 |
and if you use the program, he is your master." Richard Stallman |
Archives