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

Support for basher[1] to install prm. #4

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

heynemann
Copy link

basher[1] is a package manager for bash scripts and functions.
This change allows the installation of this script using:

basher install eivind88/prm

[1] https://github.com/basherpm/basher

basher is a package manager for bash scripts and functions.
This change allows the installation of this script using:

    basher install eivind88/prm

[1] https://github.com/basherpm/basher
@EivindArvesen
Copy link
Owner

I'm thinking this should append an alias to the user .bashrc or .bash_profile, or at the very least echo a message about proper usage (e.g. propose that the user make an alias) post install, as prm must be sourced to work properly (see readme).

@EivindArvesen
Copy link
Owner

Also: why the second commit (login shell)?

@heynemann
Copy link
Author

Terribly sorry. Disregard this PR. I committed the login change by
accident.

But with basher installing it is much easier. And all you need is a bin
folder.

That's why I thought it would be useful.
Em 19/09/2015 12:53, "Eivind Arvesen" notifications@github.com escreveu:

Also: why the second commit (login shell)?


Reply to this email directly or view it on GitHub
#4 (comment).

@EivindArvesen
Copy link
Owner

Ok.

I agree that installation via a package manager is an optimal solution, and have opened an issue related to this, but this needs to include an append (alias) to a user dotfile or at least a message regarding proper use of prm (i.e. sourcing the script), e.g. via a post-install hook.

Byt the way – since I have no experience with basher – how does it compare to the alternatives outlined in the issue (i.e. OS-specific, as opposed to language-specific) and their prevalence/popularity?

@heynemann
Copy link
Author

Basher includes it in the user's PATH.

That way there's no need to change bashrc.
Em 19/09/2015 22:11, "Eivind Arvesen" notifications@github.com escreveu:

Ok.

I agree that installation via a package manager is an optimal solution,
and have opened an issue #5
related to this, but this needs to include an append (alias) to a user
dotfile or at least a message regarding proper use of prm (i.e. sourcing
the script), e.g. via a post-install hook.

Byt the way – since I have no experience with basher – how does it compare
to the alternatives outlined in the issue (i.e. OS-specific, as opposed to
language-specific) and their prevalence/popularity?


Reply to this email directly or view it on GitHub
#4 (comment).

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.

None yet

2 participants