| 1 |
On Sat, 23 Jun 2012 22:27:03 +0300 |
| 2 |
Alex Alexander <wired@g.o> wrote: |
| 3 |
> On Sat, Jun 23, 2012 at 10:16 PM, Ciaran McCreesh |
| 4 |
> <ciaran.mccreesh@××××××××××.com> wrote: |
| 5 |
> > On Sat, 23 Jun 2012 22:14:32 +0300 |
| 6 |
> > Alex Alexander <wired@g.o> wrote: |
| 7 |
> >> If it is a package without reverse dependencies, updating to the |
| 8 |
> >> most recent slot and/or version should be expected unless the user |
| 9 |
> >> has the slot defined in the world file. |
| 10 |
> > |
| 11 |
> > That's the part that no longer holds. The package mangler now needs |
| 12 |
> > a way of knowing that for a certain few packages, bringing in new |
| 13 |
> > slots when not explicitly required is undesirable. |
| 14 |
> |
| 15 |
> Or the PM can notify the user that a new slot has come up and instruct |
| 16 |
> them to specify their desired slot in their world file. |
| 17 |
|
| 18 |
But why? The package mangler could automatically do the right thing, |
| 19 |
without requiring help from a user who probably doesn't know about all |
| 20 |
of this, if only the small number of packages that did funky things |
| 21 |
with revisions and slots said so. |
| 22 |
|
| 23 |
-- |
| 24 |
Ciaran McCreesh |
Archives