You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Spec file format doesn't describe the expressions implemented e.g. for Requires. There are several operators like and, or, if, unless, else, with and without.
Example:
Requires: ( pkgA >= 1.2.3 or pkgB )
The text was updated successfully, but these errors were encountered:
I suggest looking at the top-level manual for a wider perspective of what's documented. You'll find multiple articles on dependencies there, including one on boolean dependencies: https://rpm-software-management.github.io/rpm/manual/
The way our manual is constructed leaves a lot to be desired for sure, for proper organization it'd call for something other than bunch of files in markdown really. Besides historical reasons, there's a reason why dependencies are described outside spec syntax: these exist in various forms outside the spec, so documenting them as spec syntax would be overly limiting.
The Spec file format doesn't describe the expressions implemented e.g. for
Requires
. There are several operators likeand
,or
,if
,unless
,else
,with
andwithout
.Example:
The text was updated successfully, but these errors were encountered: