| 1 |
On Sat, 23 Jun 2012 17:20:23 +0300 |
| 2 |
Mart Raudsepp <leio@g.o> wrote: |
| 3 |
> > The 'standard' behaviour (which can be changed by the user) for |
| 4 |
> > Paludis when doing "complete" resolutions is that whenever there's |
| 5 |
> > a slot of something installed, it will try to bring in the newest |
| 6 |
> > version of that package, even if it's in a different slot. This is |
| 7 |
> > generally a good thing, since newer versions are supposed to be |
| 8 |
> > better than older versions. The problem is that now "newer" |
| 9 |
> > versions are being used to mean "with a different Ruby |
| 10 |
> > implementation" or "built in a different way", which screws up the |
| 11 |
> > meaning. |
| 12 |
> |
| 13 |
> Don't do that if the slotted package in question is not in the @world, |
| 14 |
> and all packages depending on it strictly require the older SLOT. |
| 15 |
|
| 16 |
That is an option Paludis provides for users, but doing so leads to old |
| 17 |
versions of things lying around when an upgrade is preferred. It's also |
| 18 |
incorrect behaviour when multiple slots are capable of satisfying a |
| 19 |
dependency. |
| 20 |
|
| 21 |
-- |
| 22 |
Ciaran McCreesh |
Archives