On Fri, 11 Nov 2016 02:31:29 +0100
Ulrich Mueller wrote:
> Also note that the suggested set of operators is incomplete. There are
> "<== less than or equal to" and ">== greater than or equal to", but
> the corresponding ones for "less than" and "greater than" are missing.
> So this would remove p
On Fri, 11 Nov 2016 00:19:16 +0100
Ulrich Mueller wrote:
> > On Thu, 10 Nov 2016, Michał Górny wrote:
>
> > The following revision-free version comparison operators are provided:
>
> > == exact version match, or prefix match (with *)
> > != exact version non-match, or prefix non-m
On Fri, Nov 11, 2016 at 6:53 AM, Michał Górny wrote:
> Hello, everyone.
>
> Following my earlier threads, I'd like to propose a first complete
> solution for new version restrictions for package dependencies. I
> honestly doubt it's going to be approved since it's a major change.
> Nevertheless, I
> On Thu, 10 Nov 2016, Gordon Pettey wrote:
>> === exact version+revision match
>> !== exact version+revision non-match
>> <== version+revision less or equal to match
>> >== version+revision greater or equal to match
> These are not necessary if the regular operators mat
On 11/10/2016 07:03 PM, Gordon Pettey wrote:
>
> Only if you're misusing revisions. A package depends on a another
> package, not the ebuild revision of that package.
>
What if your package needs mine with SSL support, but mine was initially
committed without SSL support and -r1 adds it?
On Thu, Nov 10, 2016 at 5:19 PM, Ulrich Mueller wrote:
> > On Thu, 10 Nov 2016, Michał Górny wrote:
>
> > The following revision-free version comparison operators are provided:
>
> > == exact version match, or prefix match (with *)
> > != exact version non-match, or prefix non-match (wi
> On Thu, 10 Nov 2016, Michał Górny wrote:
> The following revision-free version comparison operators are provided:
> == exact version match, or prefix match (with *)
> != exact version non-match, or prefix non-match (with *)
> <= version less or equal
Hello, everyone.
Following my earlier threads, I'd like to propose a first complete
solution for new version restrictions for package dependencies. I
honestly doubt it's going to be approved since it's a major change.
Nevertheless, I think it's an interesting topic for consideration.
What is incl
