Thank you for you answer.
I just want using `nimble` as a classic package manager. But may be i don't
have understand its goal (i begin to wonder, seeing your post and i'm serious).
A classic package manager can:
* update its database of packets (ok : `nimble refresh` )
* do a full upgrade of all installed packets (seems not possible with
`nimble`)
* remove outdated packets (seems not possible with `nimble`)
Can i do the operations above with `nimble` ?
When you say:
You should not need to update or clean packages in your pkg directory, you
do that in your *.nimble file.
Then nimble install in your project go gets the right versions.
Run
That means that each version of of package needed is installed on the fly when
needed by nimble config dependancy (with the `requires` order ?)
So that mean i could vacuum in _~ /.nimble/pkgs_ without afraiding of breaking
deps. That's good. And reading that, i understand that asking a global option
for cleaning « outdated » packages is nonsense, because differents projects
could need differents versions.
I think i understand better now, thank you.
