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

Please don't fail when CMAKE_INSTALL_PREFIX is /usr/local #1195

Closed
yurivict opened this issue May 11, 2019 · 2 comments · Fixed by #1513
Closed

Please don't fail when CMAKE_INSTALL_PREFIX is /usr/local #1195

yurivict opened this issue May 11, 2019 · 2 comments · Fixed by #1513
Assignees
Labels
I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) S: Normal Handle this with default priority T: Discussion Still searching for the right way to proceed / suggestions welcome

Comments

@yurivict
Copy link

https://github.com/nest/nest-simulator/blob/master/CMakeLists.txt#L104

There's nothing wrong with installing into /usr/local.
It normally installs into a stage directory when package is built.

@yurivict yurivict changed the title Please don;t fail when CMAKE_INSTALL_PREFIX = /usr/local Please don't fail when CMAKE_INSTALL_PREFIX is /usr/local May 11, 2019
@terhorstd terhorstd added ZC: Installation DO NOT USE THIS LABEL I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) ZP: Pending DO NOT USE THIS LABEL S: Normal Handle this with default priority T: Discussion Still searching for the right way to proceed / suggestions welcome labels Jun 3, 2019
@terhorstd
Copy link
Contributor

This is something that we should re-discuss in one of the next NEST VCs, probably after the NEST conference.

@jougs jougs self-assigned this Jul 8, 2019
@jougs
Copy link
Contributor

jougs commented Jul 8, 2019

In the Open NEST VC We have come to the conclusion that if users decide to install globally they should not be prohibited from doing so. I'll prepare and send a pull request to remove the pertaining code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) S: Normal Handle this with default priority T: Discussion Still searching for the right way to proceed / suggestions welcome
Projects
Status: Done
4 participants