Bug 176676 - spec file Requires tag: "or" in expressions
Summary: spec file Requires tag: "or" in expressions
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm
Version: 4
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Paul Nasrat
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2005-12-29 13:42 UTC by Andreas Gruenbacher
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2005-12-30 17:57:31 UTC

Attachments (Terms of Use)

Description Andreas Gruenbacher 2005-12-29 13:42:57 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.4; Linux) KHTML/3.4.2 (like Gecko)

Description of problem:
According to how I read the documentation, chapter 22.1.3. "Dependency tags" 
at http://fedora.redhat.com/docs/drafts/rpm-guide-en/ch-specfile-syntax.html 
says that RPM supports the following syntax: 
  Requires: perl(IO-Wrap) == 4.5 or perl(IO-Wrap)-4.5 
this does not actually seem to be the case. May I please ask for 
clarification: is this a planned feature that didn't get implemented yet, or 
is the documentation wrong? 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Add the above Requires tag to a spec file 
2. Build the spec file 
3. Observe the resulting requires with ``rpm -qp --requires'' or similar. 

Actual Results:  The package ends up with three requirements, which obviously makes no sense: 
  perl(IO-Wrap) == 4.5 

Expected Results:  An "either A or B" kind of requirement. 

Additional info:

Comment 1 Jeff Johnson 2005-12-30 17:57:31 UTC
rpm does not support aletrnation (i.e. ||) of requires, never has. No current plans (or need) to add the 

Either the doco you are reading is incorrect, or you are not reading correctly.

Comment 2 Michael Jennings (KainX) 2005-12-31 00:16:30 UTC
I would ask that you reconsider adding such a feature.  Nothing currently
supported allows this functionality, as discussed in the following thread:


Being able to specify a logical-OR would solve numerous common issues such as
capitalization problems (e.g., MySQL-devel vs. mysql-devel), naming convention
discrepencies (gtk+ vs. gtk1 vs. gtk), and so forth.

If I were to open an RFE for such a feature, would it be considered?  Or is this
bug considered the RFE?  (It seems more like a "documentation error" report to me.)


Note You need to log in before you can comment on or make changes to this bug.