[RFC] nimble update

[yglukhov]

It would be nice to have a way of updating all dependencies for a project in current directory. Our project uses a lot of dependencies that are changed quite often.

[dom96]

I think that will be what nimble update will do after #158 is implemented, still haven't worked that out completely but better dependency management is definitely a must-have. #88 will also come into play here.

What I envision nimble install --force to do, is to force the installation of a Nimble package even if some dependencies don't match or there is some other problem. I think it's @Araq's dream.

[yglukhov]

Lets clarify how nimble update should work then. Here's what i think.

nimble update <pkg> # same as "nimble install -y <pkg> && for dep in deps; do nimble install -y dep"
nimble update # same as above but works only when there's nimble file in PWD, and doesn't install/update the pkg itself, only dependencies

[dom96]

I think update should get a --deps/--deps-only flag. The behaviour you are suggesting would be inconsistent.

[dom96]

Demoting this to medium priority for now. I would like to hear what you think of how Nimble now installs "special" versions of dependencies ("#head" etc).

[dom96]

@yglukhov Thoughts?

Perhaps it makes sense to implement lock files first as I think this command will play an important part in that feature.

[yglukhov]

@dom96, agreed. This should be somewhere on top of lock files.

[kobi2187]

I think nimble should update packages globally, IOW, system-wise, not folder-wise.
I don't like the npm approach.
I think nimble already has a way to specify a particular version of a library, so I don't see the merit in doing it just for a specified directory.