| 1 |
On 8 September 2015 at 00:35, Marc Schiffbauer <mschiff@g.o> wrote: |
| 2 |
> I currently have this case in app-backup/obnam which is not compatible |
| 3 |
> to =dev-python/paramiko-1.13.0 |
| 4 |
> |
| 5 |
> In DEPEND I now have this: |
| 6 |
> |
| 7 |
> !=dev-python/paramiko-1.13.0 |
| 8 |
> || ( <dev-python/paramiko-1.13.0 >dev-python/paramiko-1.13.0 ) |
| 9 |
> |
| 10 |
> which does the trick, but I think much more straight forward would be: |
| 11 |
> |
| 12 |
> <>dev-python/paramiko-1.13.0 |
| 13 |
> |
| 14 |
> which would be the exact opposite of =dev-python/paramiko-1.13.0 |
| 15 |
> |
| 16 |
> An alternate syntax would be (but I'd prefer the former): |
| 17 |
> |
| 18 |
> !=dev-python/paramiko-1.13.0 |
| 19 |
> |
| 20 |
> What do you think and would is the proper way to suggest this for a new |
| 21 |
> EAPI? A new bug? On what |
| 22 |
|
| 23 |
|
| 24 |
My opposition would be I figure its more likely you want a range of |
| 25 |
exclusion, not a single version. |
| 26 |
|
| 27 |
EG: you don't really want !=dev-python/paramiko-1.13.0 , you want |
| 28 |
!=dev-python/paramiko1.13.0{,-r{0..999}} or something. |
| 29 |
|
| 30 |
But distinguishing between "Just this exact version" and "This range" is hard. |
| 31 |
|
| 32 |
Does <> Imply "and any -rversion" ? |
| 33 |
|
| 34 |
Does <> imply "and any sub-version" like ~ does ? |
| 35 |
|
| 36 |
|
| 37 |
-- |
| 38 |
Kent |
| 39 |
|
| 40 |
KENTNL - https://metacpan.org/author/KENTNL |
Archives