> From: bill lam > Sent: Tuesday, 9 November 2010 03:19 > > I am thinking of predefining a verb in standard library for > installation > of gtk front-end such as > > getgtkide_z_=: 3 : 0 > require 'pacman' > 'update' jpkg '' > 'install' jpkg 'search' jpkg 'gtk' > if. IFWIN do. > unzip @ wget gtk binary > end. > ) > > so that a fresh installation only need to run getgtkide'' if the user > want > gtk frontend.
I like the idea of batching up the steps, but wonder if (at least some of) this could be done in a less ad hoc manner by extending pacman slightly? I can imagine that there may be a number of groupings of addons that may be desirable to download as single package. I'm thinking of a "meta-addon" for pacman so that for example ... 'install' jpkg 'gtkide' ... would install a definable set of addons including: gui/gtk, ide/gtk, graphics/viewmat, graphics/plot, graphics graphics/afm, graphics/color, graphics/bmp, ... Note that... 'install' jpkg 'all' ... is already a valid option and will install *all* addons available in JAL. There may be other meta-addons that would make sense too. If the DEPENDS option in the addon manifest got automatically resolved by JAL then the meta-addon could essentially be just another addon with the appropriate dependencies specified. The only remaining thing is obviously how to handle providing the Gtk+ binaries (32- vs 64-bit?) on Windows (and perhaps Mac). It seems to me this should ideally be optional and that if possible multiple Gtk+ apps on my system should not each install their own copy of the Gtk+ binaries. Not sure how feasible that is in practise though. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
