On Thu, 31 Oct 2013 13:59:03 +0100, Sönke Ludwig wrote:
Yes, I can confirm that, unfortunately. There will be a solution for it
in the next release. The only thing is that "dub cache" seems also less
than ideal considering what it does and what it may do in the future.
My ad-hoc suggestion would be to try to solve the confusion issue by
outputting a clear message after a package has been installed, or even
by making an interactive query of the form "Package x has been installed
in y, do you want to also add it as a dependency to the package z in the
Something similar would actually be helpful to solve the inevitable next problem people have after we explain what
dub install does (did). Adding a
dub add-dependency <package> [version] which would modify their project's package.json would make things much easier than trying to explain how to modify their package.json by hand.
Another even deeper issue we sometimes see is that some people try to use dub without even having a package.json. The solution to that is probably just some improvements to the documentation.