| 1 |
On Mon, Sep 14, 2015 at 1:38 PM, Daniel Campbell <zlg@g.o> wrote: |
| 2 |
> Honestly, this situation looks like a perfect candidate for slotting |
| 3 |
> instead of adding a new feature. If SLOT is setup correctly between |
| 4 |
> ebuilds, you could check to be sure it's a specific SLOT. So in your |
| 5 |
> case, pkg-1.0.2[a-z] would be slotted with e.g. pkg-1.0.2g:1.0.2. |
| 6 |
> Anything depending on it would use `pkg:1.0.2`, and the pkg-1.0.3a |
| 7 |
> ebuild could use SLOT="1.0.3" and be called as a dependency via |
| 8 |
> `pkg:1.0.3`. |
| 9 |
Slotting means isolation (most of the time as a group and not necessarily on a |
| 10 |
parent version), but that's not always the case when you're just |
| 11 |
wanting to target |
| 12 |
a specific version. With the operator we could avoid unnecessary |
| 13 |
overkill using slots. |
| 14 |
|
| 15 |
Also that would only apply when you're creating an ebuild. |
Archives