Re: [gentoo-dev] in-place SLOT updates on ebuilds?

[Ian Stakenvicius]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 17/01/13 12:30 PM, Ciaran McCreesh wrote:
> On Thu, 17 Jan 2013 12:25:46 -0500 Ian Stakenvicius
> <axs@g.o> wrote:
>> On 17/01/13 12:15 PM, Ciaran McCreesh wrote:
>>> Ian Stakenvicius <axs@g.o> wrote:
>>>> On 17/01/13 11:47 AM, Ciaran McCreesh wrote:
>>>>>
>>>>> .... If you have foo-1:a and foo-2:b installed, and then
>>>>> you install foo-1:b, it replaces both 1:a and 2:b.
>>>>>
>>>
>>>> that would be an interesting case with portage, given if
>>>> foo-1:a moved to foo-1:b that should occur via a slot-move
>>>> shouldn't it?
>>>
>>> There's nothing forcing that to be the case.
>>>
>
>> Does an in-tree change in SLOT automatically schedule something
>> for rebuild on an emerge -uD (or equivalent command in other
>> package managers) ?  If so, does sub-slot changes also trigger
>> this?
>
> For Paludis, not necessarily (unless the user passes in -km or
> some variation): we look at the slot of the best version in the
> tree, plus the best version in the tree of each installed slot, and
> then compare versions.
>
> This is related to one of the reasons a revbump should be required
> when moving a package from EAPI 4 to EAPI 5: if a package's version
> is unchanged, then its slot changing from x to x/y isn't enough to
> force a reinstall.
>

Makes sense.  Up until this point, I had assumed that an in-place SLOT
change wouldn't trigger a rebuild on a regular update.  I haddn't
considered that it might until you mentioned your example above.

Thanks for clarifying!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iF4EAREIAAYFAlD4OEcACgkQ2ugaI38ACPAeQAD/W7DUo1C4+xJRoArFflOqO/Sb
My2htCgqONtAl5gtan0BAKh2zoOy92HyisbBfvjYzoAkLrQa0kL8SUU4Pkdu18DU
=2Os5
-----END PGP SIGNATURE-----