Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=507292
Jeff Johnson <n3npq(a)mac.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |n3npq(a)mac.com
--- Comment #1 from Jeff Johnson <n3npq(a)mac.com> 2009-06-22 15:26:17 EDT ---
FYI: Permitting a '*' wild card in Requires: version/release with
the well-defined semantic
Match everything else (i.e. return 0 from rpmvercmp)
is quite straightforward and handles most of what is commonly
desired without the implementation cost (and semantic definitions)
that need to be defined for a full blown *RE dependency matching
compatible with existing legacy RPM and *.rpm implementations.
For the record: Attaching new interpretations to a '*' character
will be treated by older RPM implementations as any other non-alpha,
non-digit, punctuation character would be treated. If the '*' is permitted
only at the end of release/version, then legacy rpm would treat the '*'
when encountered just like any pucnctuation character like '.' or "+".
Since the character is at the end of the comparison, adding a well-defined
Return 0 == match from rpmvercmp
is almost certainly not change any prior comparison.
I'll leave it to you to guess where an implementation for '*" wildcarding
in dependency comparisons might be found.
And having RE's on Provides: is exactly the same effect as adding multiple
Provides:. Write a macro if you want a compact way to generate multiple
alternative
Provides: without the bother of typing separate Provides:. That just isn't that
hard to do, nor is there any need to invent alternate Provides: syntax that
forces rpm to implement regexp EVR comparison that I'm aware of.
--
Configure bugmail:
https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.