1 |
On Sun, Nov 6, 2016 at 6:52 PM, Michał Górny <mgorny@g.o> wrote: |
2 |
> Hi, everyone. |
3 |
> |
4 |
> Following my previous RFC wrt version operator problems, I'd like to |
5 |
> start the second part of the discussion: how to improve version |
6 |
> operators in a Future EAPI? |
7 |
> |
8 |
> I've collected various ideas on operator changes on a wiki page [1]. |
9 |
> I've tried to stay open-minded and cover every possibility, even though |
10 |
> I doubt some of them would be even considered. |
11 |
> |
12 |
> I should warn you that some of the solutions are interlinked to each |
13 |
> other, and you probably need to look through the whole page first |
14 |
> before starting to construct an opinion. For example, specific |
15 |
> solutions to most of the problems depend on whether we enable version |
16 |
> ranges and in which form. |
17 |
> |
18 |
> I think we should start by loosely discussing the various ideas |
19 |
> on the wiki page. Feel free to also point out any missing ideas |
20 |
> or remarks that would be useful there. |
21 |
> |
22 |
> So, what are your comments? |
23 |
> |
24 |
> [1]:https://wiki.gentoo.org/wiki/Future_EAPI/Version_syntax_changes |
25 |
> |
26 |
> -- |
27 |
> Best regards, |
28 |
> Michał Górny |
29 |
> <http://dev.gentoo.org/~mgorny/> |
30 |
|
31 |
I also like the idea of moving the operator as it's more consistent |
32 |
and opens new doors to other solutions. |
33 |
|
34 |
As for the use of operator & and |, they're quite good, but I'd prefer |
35 |
the use of Gmail's style where expressions placed in () are processed |
36 |
with AND, and expressions placed inside {} are processed with OR: |
37 |
|
38 |
dev-foo/bar[>=1.3&<1.5] dev-foo/bar(>=1.3 <1.5) |
39 |
dev-foo/bar[>=1.3&<1.5&!=1.4.1] dev-foo/bar(>=1.3 <1.5 !=1.4.1) |
40 |
dev-foo/bar[<1.1|>=1.5] dev-foo/bar{<1.1 >=1.5} |
41 |
dev-foo/bar[=1.1*|=1.3*|>=1.5] dev-foo/bar{=1.1* =1.3* >=1.5} |
42 |
|
43 |
I find it more readable. The former looks too compressed. |
44 |
|
45 |
-- |
46 |
konsolebox |