The same package might have multiple sources (several git repositories, local repos etc) - as such, when running nimble develop --withDependencies and creating packages in vendor/, the name of the folder should reflect the canonical name of the package.
This also requires treating one of the sources as "canonical" because this will become git origin while the other sources (if they are also git-based), could be added as separate remotes.
The same package might have multiple sources (several git repositories, local repos etc) - as such, when running
nimble develop --withDependenciesand creating packages invendor/, the name of the folder should reflect the canonical name of the package.This also requires treating one of the sources as "canonical" because this will become
git originwhile the other sources (if they are also git-based), could be added as separate remotes.