Allow installing into custom directory #1188
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Allows the user to install the built package into a different directory than
/usr/localby setting thePREFIXenvironment variable.I want to keep my manually installed packages easy to upgrade and remove, so I use GNU Stow for that purpose. I install the package to
/usr/local/stow/<name>(where<name>is some arbitrary name I chose), then have Stow create symlinks intousr/local. Stow owns these symlinks and if I want to remove or replace a package it knows exactly which symlinks to remove.This is much better than having a number of files from various packages lying all around the system. erlang_ls is not bad, it has only two files, but even two files here and two files there can quickly add up.