-
-
Notifications
You must be signed in to change notification settings - Fork 75
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
feature request: easy updates #15
Comments
Hi @magnetophon Thanks so much for filing this issue, it has definitely come to my attention that this is indeed a limitation currently. One which I myself am not confronted with as seeing as the author of this plugin I have a copy of the repo laying around on all my machines. I'll implement your suggestion to include a comment for now, and think about how we can improve the update process. |
Dank je wel! |
I thought about this some more and I think that wrapping this plugin in a PyPy package could be a potential improvement, the only trick would be to get the files in the resources for my own reference sake:
This would allow for the following installation flow:
The second command would actually symlink the files to the ranger directory, so that a future Removal of the plugin could be done like this:
@magnetophon would a flow as outlined above meet you're expectations of a easier update/installation/removal process ? |
Sounds great, thanks! |
Closed by #37 |
Cool, thanks! |
Is there a way to keep this wonderful plugin up to date that doesn't involve manually checking this repo?
As a partial solution I suggest changing the line that is inserted to
rc.conf
to include where the plugin came from:That way, when you update ranger, and diff
rc.conf
, you are reminded to have a look here.The text was updated successfully, but these errors were encountered: