1 |
On Sat, 23 Jun 2012 21:37:11 +0100 |
2 |
Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> wrote: |
3 |
|
4 |
> On Sat, 23 Jun 2012 22:36:14 +0200 |
5 |
> Marien Zwart <marienz@g.o> wrote: |
6 |
> > On za, 2012-06-23 at 17:08 +0100, Ciaran McCreesh wrote: |
7 |
> > > > Is it that Paludis installs a newer SLOT even if a reverse |
8 |
> > > dependency |
9 |
> > > > explicitly requests another SLOT? Sounds like a bug to me. |
10 |
> > > |
11 |
> > > No, it's that if a user requests a "complete" resolution, Paludis |
12 |
> > > installs the newest version of things that it can. Extensive |
13 |
> > > consultation with users has shown that this is a good behaviour, |
14 |
> > > except |
15 |
> > > in the small number of situations that have recently arisen where |
16 |
> > > people are doing weird things with versions and slots. |
17 |
> > |
18 |
> > It surprises me that this behavior is normally desirable for |
19 |
> > packages where all dependencies (including any in the world set or |
20 |
> > the like) are slotted. |
21 |
> |
22 |
> Think || ( a:3 a:2 ). |
23 |
|
24 |
So now that you've stated the problem, maybe it's a good time to find |
25 |
a proper solution for it. |
26 |
|
27 |
-- |
28 |
Best regards, |
29 |
Michał Górny |