-
Notifications
You must be signed in to change notification settings - Fork 190
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
nimble allows installing package with same name #573
Comments
Any proposals on how to fix this? |
The easiest way would be to not allow to install the package if a package with same name and different author (is the author name unique enough?) already exists. Of course this has downsides but I don't see a better solution when importing by url scheme (like Go supports) is not supported ( For the referenced issue I think it should be allowed and if author is same and package version is greater install normal way, if package author is different then only the package which explicitly depends on the package by url should load this dependency. When "importing by url scheme as string" would be supported only packages that were installed by package name should be importable by package name (because they came from nimbles official list and are unqiue there) all others woud be forced to import by url scheme. |
can't we specify an alias on nimble level |
Import by url would require a major change in the Nim language. |
I'm going to merge this into #574, these issues are pretty similar. I've put my thoughts on how to fix this in there (I think we should look at repo URL for uniqueness). |
When installing two packages from different sources and different authors but with same name, it works if the package which gets installed has a greater version number.
TheOne problem is thatnim
doesn't support loading the package anymore.Example:
nimble install https://github.com/ephja/lzma
installslzma@0.1.0
nimble install https://github.com/tim-st/nim-lzma@#test-nimble-version
installslzma@0.1.1
import lzma
fails withcannot open file lzma
now.The text was updated successfully, but these errors were encountered: