Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BuildRequires does not support boolean operators #1216

Closed
jcsiadal opened this issue May 13, 2020 · 2 comments
Closed

BuildRequires does not support boolean operators #1216

jcsiadal opened this issue May 13, 2020 · 2 comments

Comments

@jcsiadal
Copy link

When using the following tag:
BuildRequires: (pkgA or pkgB)
rpmbuild will flag "(PkgA," "pkgB)", and "or" as not found. Removing the parenthesis doesn't resolve the issue. Tested with rpmbuild 4.13 and 4.15.1.

It doesn't seem logical to support the use of boolean operators on installation dependencies at run time, but not to support them at build time. If not supporting this is by design, then rpmlint is failing to flag the use of conditionals in BuildRequires as an error.

I discovered this while building an RPM with a dependency met by either an OS package or the package provided by the product vendor using a different name. Neither RPM "Provides" anything other than their own package names.

@ignatenkobrain
Copy link
Contributor

Can you provide a reproducer? We use rich dependencies in BuildRequires at least in 2000 packages in Fedora.

@jcsiadal
Copy link
Author

Thanks for the fast response. I have to take a mea culpa on this one; I went to rerun the build for exact output and it worked. I spent two hours this morning on two different servers and couldn't get this to work. It works now and I have no idea what changed.

FYI, I went through docs on rpm.org and fedora before posting the issue. Requires, Recommends, and the other dependencies were explicitly listed as supporting Booleans, but BuildRequires was noticeably missing. With the issues I was having, I concluded it may have been left out.

In any case, I'll close this issue. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants