-
Notifications
You must be signed in to change notification settings - Fork 227
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
jpm support other VCS #631
Comments
Agreed. I think it would be good to start with something simple like tarball support, but to add more artifact types it becomes needed to start bundling binary code into jpm, or rely on the user having a variety of binaries on their system. On posix it is fine to assume core utils I think, but windows is a different story. |
I might be wrong, but i think windows 10 might come with tar and curl now. |
An alternative to adding a # current
:dependencies [{:repo "https://github.com/joy-framework/joy" :tag "0.5.2"}]
# proposed
:dependencies [{:git "https://github.com/joy-framework/joy" :tag "0.5.2"}
{:tar "https://example.org/dep.tar"}] If you have a struct with conflicting keys (e.g. both As for supporting different tools, |
@pyrmont jpm now supports a |
@bakpakin I'm looking at janet-lang/jpm and # dictionary
{:repo "https://example.org/dep.tar" :type :tar}
# string
"tar::https://example.org/dep.tar" Is that right? |
Going through my backlog and saw this. @pyrmont , Yes, that is the case here. The string syntax is for command line installs |
Got it. Thanks! |
I think the lockfile and also jpm file format is heavily biased towards git. Not sure the best approach to address this, but perhaps at a minimum the lockfile format should have a :kind field or something to disambiguate.
The text was updated successfully, but these errors were encountered: