Gentoo Archives: gentoo-dev

From: Gordon Pettey <petteyg359@×××××.com>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: [RFC] New version constraints: variant one
Date: Fri, 11 Nov 2016 00:03:42
Message-Id: CAHY5MeeSg4cr=2pxJQDouf+6_RhjTB++WA4vcif2ph6bQf+VuA@mail.gmail.com
In Reply to: [gentoo-dev] Re: [RFC] New version constraints: variant one by Ulrich Mueller
1 On Thu, Nov 10, 2016 at 5:19 PM, Ulrich Mueller <ulm@g.o> wrote:
2
3 > >>>>> On Thu, 10 Nov 2016, Michał Górny wrote:
4 >
5 > > The following revision-free version comparison operators are provided:
6 >
7 > > == exact version match, or prefix match (with *)
8 > > != exact version non-match, or prefix non-match (with *)
9 > > < version less than match
10 > > <= version less or equal to match
11 > > > version greater than match
12 > > >= version greater or equal to match
13 >
14 > I think we should stick to the existing operators, and not introduce
15 > two slightly different sets for different contexts.
16 >
17 > Especially:
18 > - The operator for exact version match should be = not ==.
19 > - Omit the != operator because it can be confused with blockers. If an
20 > operator for inequality is needed, we can add one but it should work
21 > everywhere (we could e.g. use <> for that).
22 > - The ~ operator is missing.
23 >
24 > > All those operators compare on versions ignoring the revision part.
25 >
26 > I am strictly opposed to this. Again, it is confusing to have the same
27 > operators acting in a different way depending on context.
28 >
29 > > The following revision-oriented version comparison operators are
30 > > provided:
31 >
32 > > === exact version+revision match
33 > > !== exact version+revision non-match
34 > > <== version+revision less or equal to match
35 > > >== version+revision greater or equal to match
36 >
37 > These are not necessary if the regular operators match revision.
38 >
39
40 Only if you're misusing revisions. A package depends on a another package,
41 not the ebuild revision of that package.

Replies