| 1 |
* Kent Fredric schrieb am 07.09.15 um 15:18 Uhr: |
| 2 |
> On 8 September 2015 at 00:35, Marc Schiffbauer <mschiff@g.o> wrote: |
| 3 |
> > What do you think and would is the proper way to suggest this for a new |
| 4 |
> > EAPI? A new bug? On what |
| 5 |
> |
| 6 |
> |
| 7 |
> My opposition would be I figure its more likely you want a range of |
| 8 |
> exclusion, not a single version. |
| 9 |
> |
| 10 |
> EG: you don't really want !=dev-python/paramiko-1.13.0 , you want |
| 11 |
> !=dev-python/paramiko1.13.0{,-r{0..999}} or something. |
| 12 |
|
| 13 |
Erm. +1 |
| 14 |
You are of cause right. So you just discovered a potential bug in my |
| 15 |
ebuild :-P |
| 16 |
|
| 17 |
> |
| 18 |
> But distinguishing between "Just this exact version" and "This range" is hard. |
| 19 |
> |
| 20 |
> Does <> Imply "and any -rversion" ? |
| 21 |
> |
| 22 |
> Does <> imply "and any sub-version" like ~ does ? |
| 23 |
|
| 24 |
Well, than I might change my mind and prefer != over <> as it would be |
| 25 |
more flexible: |
| 26 |
|
| 27 |
!=foo/bar-1 => exact version |
| 28 |
!~foo/bar-1 => that version and any revision |
| 29 |
|
| 30 |
And as the cherry on the cake theere could be |
| 31 |
|
| 32 |
<> ( foo/bar-1 foo/bar-5 ) |
| 33 |
|
| 34 |
To express real ranges (that would include revisions) |
| 35 |
|
| 36 |
-Marc |
| 37 |
|
| 38 |
-- |
| 39 |
0x35A64134 - 8AAC 5F46 83B4 DB70 8317 |
| 40 |
3723 296C 6CCA 35A6 4134 |
Archives