-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
Git dependencies #344
Git dependencies #344
Conversation
- support git dependencies is haxelib.json - do not delete git dependency folder, it's pointless. - auto update git subdependencies
…pendencies we could go into infinite loop of removing and cloning again
… was requested before ask if it should be overwritten
Thanks. Would you take a look at the failed test and try to fix it?
|
Fixed. |
Hey, thanks for the contribution. Could you add a check that vcs dependencies aren't allow when submitting to haxelib?
Not sure I fully get what that means, you can't have two branch of the same repository used as deps by different libs/project? |
Yep, the check makes sense. I'll look at it.
Correct. In the discussion for #238 it was decided to not bother with this and support just one because it already brings quite a lot of value (#238 (comment) and #238 (comment)). |
So I did some digging through the code and testing and there already is a "check"... submit fails with ie.: |
The error message could be improved but it's still descriptive enough. @nadako I haven't tried it yet but the design and code are good, what do you think? |
lgtm, ship it! |
Git dependencies behavior as discussed in #238 :
haxelib install haxelib.json
and dependencies from the json will be installedgit:<url>#commit-ish
... if so git dependency will be installed, this is possible in both json and hxml definitionscommit-ish
is defined and/or different than one already installed from same json/hxml (ie. because of dependency of dependency) user is prompted to confirm overwriting existing git version