The original discussion of JRepo's commands noted that install would merely do that.  We believe it would be preferable if, in addition to installing, it checked if the module's dependencies were satisfied.  While it might not be possible to do 100% accurate check, some simple checking is possible.  For example, it will be difficult (at best) to check a module's requirements if it has a custom import policy (in which case, JRepo could inform the user of that policy's presence).

If a -q flag is given, installing a module should *not* do the checking; this is presumably useful when a person or script is installing several modules and anticipates that their dependencies would not be satisfied given the order of installation.

Note also that post-installation checking might be done via the (proposed) JRepo commands "dependencies" or "check".
Posted Date : 2007-08-07 18:43:39.0

N/A

If a dependency cannot be satisfied, the newly-installed module won't be installed, unless the -q flag is provided.
Posted Date : 2008-07-30 18:44:39.0

http://webrev.invokedynamic.info/bristor/jrepo.02/
Posted Date : 2008-08-19 19:28:05.0