Not saying that it wouldn't be useful to extend pacman to support this better but just in case you're not aware, you can download the individual zips from:
http://www.jsoftware.com/jal/j701/addons/ unzip them to your ~addons folder and they should work. Rebuild your local catalog to make sure they show up in pacman. > From: greg heil > Sent: Wednesday, 10 November 2010 12:14 > > Yes some (multiple?) packages which can sneakernetted through to a > Faraday caged machine. That machine should be fully useful and fluent > J-wise. > > greg > ~krsnadas.org > > -- > > from Sherlock, Ric <[email protected]> > reply-to Beta forum <[email protected]> > to Beta forum <[email protected]> > date 9 November 2010 14:58 > subject Re: [Jbeta] pacman permissions > > Just wanted to confirm that you mean more than just the ability to > interact with pacman while offline? (which pacman already does) > > You mean you want to be able to copy a zip file (downloaded from JAL) > to an offline machine that it can use to update its local catalog? > > -- > > From: greg heil > Sent: Wednesday, 10 November 2010 11:48 > > options require internet access > > Yes, there should/needs to be access for a 'clean-room' machine, one > which can/does not have continuous internet access. A zip file or a > like snapshot would satisfy this need. > > greg > ~krsnadas.org > > -- > > from Sherlock, Ric <[email protected]> > date 9 November 2010 14:20 > > The GUI interfaces for pacman in J602, J701 jhs and J701 gtk all > currently check to see if you have "Administrator" writes to the > ~addons folder before letting you run pacman. I think this is a > mistake. The user should be able to open pacman and browse the > available addons and see what is installed/not installed without > requiring write access. > > IMO rather than "fail" if 'update' fails due to checkaccess, the > attempt to start pacman should succeed, but perhaps there should be a > message explaining that the "local catalog was last updated x days > ago". > > From the following page > http://www.jsoftware.com/jwiki/JAL/Package%20Manager/jpkg > > The following options require write access to the ~addons directory: > > 'remove' > > The following options require internet access as well as write access > to the ~addons directory: > > 'install' , 'reinstall' , 'update' , 'upgrade' > > All other options only require read access to the ~addons directory. > (history, manifest, show, search, showinstalled, shownotinstalled, > showupgrade, status ) > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
