| 1 |
On 05/08/13 18:00, Michael Palimaka wrote: |
| 2 |
> On 5/08/2013 21:58, Samuli Suominen wrote: |
| 3 |
>> On 05/08/13 13:56, Michael Palimaka wrote: |
| 4 |
>>> On 5/08/2013 19:33, Samuli Suominen wrote: |
| 5 |
>>>> This is a friendly reminder. |
| 6 |
>>>> |
| 7 |
>>>> I've found the tree again to have dependencies like: |
| 8 |
>>>> |
| 9 |
>>>> dev-libs/openssl:= |
| 10 |
>>>> virtual/jpeg:= |
| 11 |
>>> |
| 12 |
>>> Is there any reason for the subslot operator being specified at all? I |
| 13 |
>>> don't see those packages defining any subslots. |
| 14 |
>> |
| 15 |
>> You don't need to see it, because portage sets implicit subslot /0 in |
| 16 |
>> EAPI="5" so it's there, even if you don't see it. |
| 17 |
>> Then when it's changed (= set), the effect is same. |
| 18 |
>> |
| 19 |
>> - Samuli |
| 20 |
>> |
| 21 |
>> |
| 22 |
>> |
| 23 |
> |
| 24 |
> Even though the subslot is implicit, is that any reason to still use the |
| 25 |
> operator? We don't know what the maintainer's future intentions for the |
| 26 |
> subslot will be. |
| 27 |
> For example, we caused many useless rebuilds with poppler because |
| 28 |
> dependants added the subslot operator without consideration (many |
| 29 |
> packages link only against one of the stable interface libraries, rather |
| 30 |
> than the main library for which the subslot was intended). |
| 31 |
|
| 32 |
The plan is to change SLOT of virtual/jpeg from "0" to eg. "0/1" after |
| 33 |
next SONAME change in the default of the virtual, so it's useful to have |
| 34 |
everything depend on virtual/jpeg:0= ready, to get the benefits of the |
| 35 |
subslot. |
| 36 |
This is different than poppler, this is just single shared library |
| 37 |
package, like eg. libpng, tiff, lcms, ... where as poppler has many |
| 38 |
different backends and own libraries for them. |
Archives