4 Sep
2012
4 Sep
'12
6:38 p.m.
On Tue, Sep 4, 2012 at 2:17 PM, Mikhail Glushenkov
I looked more closely into this, and it seems like the easiest solution is a --no-download flag for "install". It can be implemented either by exiting with error if the install plan contains packages that aren't already installed (forcing the user to run "install --only-dependencies") or by somehow coaxing the constraint solver into rejecting such packages (is this possible?).
Would that be equivalent of configure && build && registering or are there some subtle differences. I'm worried that if there are builds my fail for confusing reasons. -- Johan