| 1 |
On Tue, Sep 15, 2015 at 2:12 AM, Kristian Fiskerstrand <k_f@g.o> wrote: |
| 2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 3 |
> Hash: SHA512 |
| 4 |
> |
| 5 |
> On 09/14/2015 06:35 AM, konsolebox wrote: |
| 6 |
>> So my suggestion is to add ~> as another operator. With it we can |
| 7 |
>> have an expression like '~>pkg-1.0.2a' and it would be equivalent |
| 8 |
>> to '>=pkg-1.0.2a' and '<pkg-1.0.2b'. Another expression like |
| 9 |
>> '~>pkg-1.0.2' would be equivalent to '>=pkg-1.0.2' and |
| 10 |
>> '<pkg-1.0.3'. |
| 11 |
> |
| 12 |
> It strikes me that this likely is better solved using subslots, if it |
| 13 |
> is ABI compatability you're wishing to retain? |
| 14 |
|
| 15 |
Subslots are only applicable when creating ebuilds. And if I'm |
| 16 |
creating an ebuild, should I wait for the dependency to have a |
| 17 |
subslot? Also like I said earlier I find that slots are more for |
| 18 |
grouping but are not really specific to a parent version. It's also |
| 19 |
not always about ABI compatibility. |
Archives