| 1 |
-----BEGIN PGP SIGNED MESSAGE-----
|
| 2 |
Hash: SHA1
|
| 3 |
|
| 4 |
On Thu, 17 Jan 2013 12:25:46 -0500
|
| 5 |
Ian Stakenvicius <axs@g.o> wrote:
|
| 6 |
> On 17/01/13 12:15 PM, Ciaran McCreesh wrote: |
| 7 |
> > Ian Stakenvicius <axs@g.o> wrote: |
| 8 |
> >> On 17/01/13 11:47 AM, Ciaran McCreesh wrote: |
| 9 |
> >>> |
| 10 |
> >>> .... If you have foo-1:a and foo-2:b installed, and then you |
| 11 |
> >>> install foo-1:b, it replaces both 1:a and 2:b. |
| 12 |
> >>> |
| 13 |
> > |
| 14 |
> >> that would be an interesting case with portage, given if foo-1:a |
| 15 |
> >> moved to foo-1:b that should occur via a slot-move shouldn't it? |
| 16 |
> > |
| 17 |
> > There's nothing forcing that to be the case. |
| 18 |
> > |
| 19 |
> |
| 20 |
> Does an in-tree change in SLOT automatically schedule something for |
| 21 |
> rebuild on an emerge -uD (or equivalent command in other package |
| 22 |
> managers) ? If so, does sub-slot changes also trigger this? |
| 23 |
|
| 24 |
For Paludis, not necessarily (unless the user passes in -km or some
|
| 25 |
variation): we look at the slot of the best version in the tree, plus
|
| 26 |
the best version in the tree of each installed slot, and then compare
|
| 27 |
versions.
|
| 28 |
|
| 29 |
This is related to one of the reasons a revbump should be required when
|
| 30 |
moving a package from EAPI 4 to EAPI 5: if a package's version is
|
| 31 |
unchanged, then its slot changing from x to x/y isn't enough to force a
|
| 32 |
reinstall.
|
| 33 |
|
| 34 |
- --
|
| 35 |
Ciaran McCreesh
|
| 36 |
-----BEGIN PGP SIGNATURE-----
|
| 37 |
Version: GnuPG v2.0.19 (GNU/Linux)
|
| 38 |
|
| 39 |
iEYEARECAAYFAlD4NSAACgkQ96zL6DUtXhE92gCgh6sNJWx2ZlrkwGTpN4r5m60c
|
| 40 |
4zsAn2o29W+4n9AzT3fVcGbVZOZ3vP3a
|
| 41 |
=ZRrl
|
| 42 |
-----END PGP SIGNATURE----- |
Archives