Good suggestion, but beyond the scope of the current release. To work there needs to be a much tighter connection between require/jal/dependencies. But clearly the direction things are moving in.
On Wed, Jan 26, 2011 at 11:59 AM, Raul Miller <rauldmil...@gmail.com> wrote: > Currently the jal page in jhs requires the user individually select > each package to be installed. > > But many people will be using jhs in the same context they would be using > jal. > > So instead of forcing the user to go to jal and find packages needed > to make something else run, perhaps a variation require could do the > work. If the package is not loaded, this 'require' could run jal and > install the package. > > Of course, it's never that simple. Sometimes the jal identifier does > not match the library name, which I suppose would require a table > lookup given a normalized version of the library name. Sometimes you > need a certain version and want an upgrade if an older version is > present, which would need some way of specifying versions. Sometimes > the internet will not be accessible. Some people might want to > intervene and manually decide whether or not to permit such upgrading. > > Still, perhaps we can see the current difficulties in using jal as a > sign that perhaps an alternative approach would be better for users? > > Thanks, > > -- > Raul > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
