-
Notifications
You must be signed in to change notification settings - Fork 257
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
Standard installation method #983
Comments
You're more than welcome to work with @amtoine @kubouch and others on nupm to extend it to work this way, assuming they approve. You're also welcome to roll-your-own and we can store it here in nu_scripts somewhere. I'd just personally rather get all the package-manager code working in the same direction so that the entire community could benefit from it. So, I'd push for nupm to allow something like you're talking about. |
Thanks, I'll close this in favour of nushell/nupm#110 |
While I fundamentally agree, I've been struggling with that for a while now. It almost seems to me that nupm is fundamentally designed in a different direction, and I haven't figured out yet myself if the "registry" based approach of nupm can be reconciled with a At this point my personal view is that it might make more sense to start a separate project with Git-centric approach and then see if there's some way to merge them in the future. |
Let's continue this conversation over at nushell/nupm#110 |
I know it's easy to install the scrips in this repo by cloning and then using
use
orsource
to activate the desired script. That's all fine.But I'm starting to collect a few Nushell-related repos like this and would like some sort of package manager to maintain them. https://github.com/nushell/nupm seems promising, but it doesn't seem to support arbitrary Git repos. I know from my BASH/ZSH days that a lot of the plugin managers will happily support the https://github.com/ohmyzsh/ohmyzsh project, which seems similar to this
nu_scripts
repo, in that it's a collection of useful scripts that doesn't necessarily conform to any packaging standard.Basically I'd like:
If this doesn't exist yet, that's fine. I'm just interested to know where Nushell is at. I'd actually be interested in building it if it was in keeping with Nushell philosophy.
The text was updated successfully, but these errors were encountered: