-
Notifications
You must be signed in to change notification settings - Fork 3
rebar-only git dependencies are detected as mix projects #12
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
Comments
Interesting. I get an earlier error with that package, because it looks like rebar is attempting to modify my global (read-only, because nix) git config! This is obviously not ideal as many users will be using nix to manage their git config. It's orthogonal to your issue, though. Thanks for the PR - will take a look.
|
Yeah, that is less than ideal. I forked their repo and have cleaned a few things up, including that git config call. |
FYI, this is only resolved for github but not git repositories. |
For example, adding this dep
Results in
Which will not build, as the repo https://github.com/klarna/mnesia_eleveldb has no mix project file.
It looks like mix doesn't put the build manager in the lock file even if specified with
manager: :rebar3
, but could deps_nix maybe inspect the out path after fetching to verify?The text was updated successfully, but these errors were encountered: