> Saying that I observe an ambiguity on the term "update" for nimble packages. > If I understood correctly a package developer registers the package with > nim-lang/packages and stores it on github. When someone installs the package, > files are downloaded from the github repo. Now, the ambiguity starts here. As > I experienced myself too, whenever you ask to install the package, it > downlods the files with the latest commit, even if the version numbers > declared in the nimble file are same. Thus, two computers with the same > package file version may have different files. I think this is undesirable > for production quality and code maintainability.
That's not how it's supposed to work, and I can't reproduce what you describe. From the nimble docs: > Nimble always fetches and installs the latest version of a package. Note that > latest version is defined as the latest tagged version in the Git (or > Mercurial) repository, if the package has no tagged versions then the latest > commit in the remote repository will be installed. If you already have that > version installed, Nimble will ask you whether you wish it to overwrite your > local copy. > > You can force Nimble to download the latest commit from the package's repo, > for example: > > $ nimble install nimgame@#head So by default, Nim will install the latest tagged release, which is not ambiguous. Only if the package doesn't use tags or the user explicitly wants the last commit will be used.
