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

Installation.md: Zsh-plugin method which doesn't require root access #703

Merged
merged 1 commit into from Mar 2, 2018
Merged

Installation.md: Zsh-plugin method which doesn't require root access #703

merged 1 commit into from Mar 2, 2018

Conversation

psprint
Copy link
Contributor

@psprint psprint commented Mar 1, 2018

A short section to Installation.md. It describes how to install as Zsh plugin. Benefits of such method:

  • no administrator access required (easy install on e.g. digital ocean, etc.),
  • declarative method of installing – 2 lines in .zshrc lead to git-extras on each account.

@spacewander
Copy link
Collaborator

@psprint
So the zplugin will take over the upgrade of git-extras?
Should we also apply a patch as what we have done with Homebrew?
https://github.com/tj/git-extras/blob/master/brew-release.patch
https://github.com/tj/git-extras/blob/master/.travis.yml#L9

@spacewander
Copy link
Collaborator

Now I think we should have the same patch instead of xxx-release.patch. We could use some unix command to update the patch according to the package manager specified via Makefile arguments.

@psprint
Copy link
Contributor Author

psprint commented Mar 2, 2018

Yes Zplugin will update. Here is more detailed description. I've tested git-extras update and it works normally, because files are in $HOME, writable. Issuing zplugin update tj/git-extras will update too, not to latest tag but to HEAD, but that's not a problem. So I think the patch isn't needed.

@spacewander spacewander merged commit 420c678 into tj:master Mar 2, 2018
@spacewander
Copy link
Collaborator

@psprint
Good news to know. Already merged, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants