Skip to content
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

When there are conflicting libraries #186

Open
XANOZOID opened this issue Jul 11, 2023 · 0 comments
Open

When there are conflicting libraries #186

XANOZOID opened this issue Jul 11, 2023 · 0 comments

Comments

@XANOZOID
Copy link

Hello!

I noticed that if you're running lix to install a lix project that it updates the projects you have. This is good. However, if you have two projects that make use of the same lix lib there is nothing taken into account. Whatever the last installed libs dependent versions take precedence.

Maybe there should be a way to detect when getting a different version of a library installed to your project that it may introduce a dependency conflict. Or at least after installing it tells you what lix libs have unmet dependencies.

One example where this is a problem is in mvcoconuts react native example. It seems like there's no way to update the dependencies in this project right now without one thing breaking or another. That is, the order in which things depend on what is not really there.. if it could be that is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant