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

Clarify consequences of running setup.py manually #1009

Merged
merged 1 commit into from
May 23, 2019

Conversation

nickolai-voyage
Copy link
Contributor

Suggesting that the two installs will "influence each other" is incorrect. In most cases the version installed by setup.py will be ignored if the setup.sh script is sourced, but I believe it is better to inform users more accurately as opposed to imposing a blanket ban. This language should also help users who have run setup.py manually understand what their options are in terms of rectifying their situation.

Suggesting that the two installs will "influence each other" is incorrect. In most cases the version installed by setup.py will be ignored if the setup.sh script is sourced, but I believe it is better to inform users more accurately as opposed to imposing a blanket ban. This language should also help users who have run setup.py manually understand what their options are in terms of rectifying their situation.
@dirk-thomas
Copy link
Member

Thanks for the improvement.

@dirk-thomas dirk-thomas merged commit 94c7d2e into ros:kinetic-devel May 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants