| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 17/01/13 12:15 PM, Ciaran McCreesh wrote: |
| 5 |
> Ian Stakenvicius <axs@g.o> wrote: |
| 6 |
>> On 17/01/13 11:47 AM, Ciaran McCreesh wrote: |
| 7 |
>>> |
| 8 |
>>> .... If you have foo-1:a and foo-2:b installed, and then you |
| 9 |
>>> install foo-1:b, it replaces both 1:a and 2:b. |
| 10 |
>>> |
| 11 |
> |
| 12 |
>> that would be an interesting case with portage, given if foo-1:a |
| 13 |
>> moved to foo-1:b that should occur via a slot-move shouldn't it? |
| 14 |
> |
| 15 |
> There's nothing forcing that to be the case. |
| 16 |
> |
| 17 |
|
| 18 |
Does an in-tree change in SLOT automatically schedule something for |
| 19 |
rebuild on an emerge -uD (or equivalent command in other package |
| 20 |
managers) ? If so, does sub-slot changes also trigger this? |
| 21 |
|
| 22 |
-----BEGIN PGP SIGNATURE----- |
| 23 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 24 |
|
| 25 |
iF4EAREIAAYFAlD4NBoACgkQ2ugaI38ACPAjrAD+JaecoYoJGj5hXFp5c1mSegFb |
| 26 |
5P0RQcD4ariRVtycWYoA/3RpgyFO/HgMlR+JSHg5kuXe9GfwRdpq6SopHbHM1n/V |
| 27 |
=y3wq |
| 28 |
-----END PGP SIGNATURE----- |
Archives