Enable/disable pyzfs explicity in spec #8179
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add --with/without pyzfs to rpm build
Explicitly enable or disable pyzfs during configure based on
what will be packaged. Configuration test should not make
packaging fail if python-cffi is installed.
Partially Addresses Issue #7882
Signed-off-by: Nathaniel Clark nathaniel.clark@misrule.us
Motivation and Context
Explicitly enable or disable pyzfs during configure based on what will be packaged. Configuration test should not make packaging fail if python-cffi is installed.
Description
If building pyzfs package, enable pyzfs in configured, and disable if not building pyzfs.
How Has This Been Tested?
Built locally on CentOS 7.4 with and without pyzfs.
Types of changes
Checklist:
Signed-off-by.