-
Notifications
You must be signed in to change notification settings - Fork 45
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
More robust recommended method to install #18
Comments
Alternative approach, which works for repos like curl \
-sSfL \
https://raw.githubusercontent.com/mapbox/logbt/v1.6.0/bin/logbt \
-o /usr/local/bin/logbt && \
chmod +x /usr/local/bin/logbt |
Usually we've pushed single files from single-script repos like this onto S3 and suggested users curl from there. https://github.com/mapbox/install-node is the primary example. Any reason that doesn't work here? |
Thanks, that works. Sounds like that is the essentially same as this idea above with the minor difference being that the single |
There is a no standard package manager for bash scripts. So we've given the recommendation for a one-liner that uses
curl
andtar
in the readme: https://github.com/mapbox/logbt#install.This issue is to summarize problems with the current approach and discuss improvements.
Current problems:
--include
(only bsdtar on osx supports --include). Ideally the install would recommend--include=bin*
such that only./bin/logbt
would be installed into/usr/local/bin/logbt
--exclude
, but this is fragile because new files added to the repo, like.travis.yml
orcircle.yml
will start getting installed into/usr/local/.travis.yml
./usr/local/.travis.yml
may easily conflict with other installs using this kind of mechanismCan't unlink already-existing object
will happen if the install tries to write over an existing file that is write protected in a directory that it does have permissions to write to.The text was updated successfully, but these errors were encountered: