>>>>> 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 match revision.
> Only if you're misusing revisions. A package depends on a another > package, not the ebuild revision of that package. A revbump can be as large a change as an upstream version bump. Usually the installed files will change, and there can be patches or even security fixes. So I don't see why we would need to double the number of operators, in order to distinguish between upstream bumps and revbumps. Note that we already have operators ignoring the revision for the two most common cases, namely ~ and >= (i.e. >=cat/foo-1 will compare with -r0, therefore ignoring the revision). 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 part of the existing functionality. Ulrich
pgpu4fH9dXHKW.pgp
Description: PGP signature
