ii14
ii14
I plan to add a lockfile, so you can just add it to your dotfiles, and yes, the intention is so when you install plugins the state of plugins from...
Actually I don't even know why I even named it a "lockfile", that's probably a wrong name. The equivalent of npm's package.json, package-lock.json or whatever it's called, where you can...
If there is a new name, maybe `plugin.{lua,json}` should be changed to `plugspec.{lua,json}` too?
> That's still the case despite what is proposed here. The point I was making is conflicts between the package names and special dependencies. If packages are kept separate from...
About that, I think the `package` field and keys for `dependencies` are going to be basically unused in actual implementations, unless there is something that I don't understand about it....
Actually wait one second, you said rocks don't need URL? So it's going to be based on what key it has? How is that supposed to work, if there is...
Anything is fine by me, as long as there is no ambiguity in what the dependency is actually supposed to be. It can be a `type` field that's *required* by...
What is the purpose of `package` name? Where clone the repository to, ie. `git clone `?
I don't think `git` is a good name for the type. It shouldn't be distinguished by where the dependency comes from, but what the package manager should do with it....
> The match against the deps package name in package.lua/json. Without it, both fields are pointless. So the package manager should assert that dependency name matches the actual package name,...