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
{{ message }}
This repository was archived by the owner on Jan 31, 2022. It is now read-only.
Due to known issues in the make process rpms or pip packages should never be built from inside a $VIRTUAL_ENV. We should add a subsection/warning/readily readable statement under the Building GEM Software section of the guide to explicitly state this.
Types of issue
Bug report (report an issue with the code)
Feature request (request for change which adds functionality)
Documentation
Expected Behavior
Should explicitly state that you should not build inside a VENV.
Current Behavior
From the commands shown it's implied that you should not build from inside a VENV (e.g. if you follow the commands verbatim you would never enter a virtual environment).
Context (for feature requests)
New developers have issues when attempting to build packages because documentation is not clear, e.g. #38. The problem is not the developer here but the documentation for lacking this key statement.
Brief summary of issue
Due to known issues in the make process
rpms orpippackages should never be built from inside a$VIRTUAL_ENV. We should add a subsection/warning/readily readable statement under the Building GEM Software section of the guide to explicitly state this.Types of issue
Expected Behavior
Should explicitly state that you should not build inside a
VENV.Current Behavior
From the commands shown it's implied that you should not build from inside a VENV (e.g. if you follow the commands verbatim you would never enter a virtual environment).
Context (for feature requests)
New developers have issues when attempting to build packages because documentation is not clear, e.g. #38. The problem is not the developer here but the documentation for lacking this key statement.
Your Environment