On Thu, Jan 14, 2016 at 10:26 PM, Tony Kelman <[email protected]> wrote: > You can add system-wide packages to LOAD_PATH while keeping the local > Pkg.dir (maybe modify the JULIA_PKGDIR environment variable for the initial > installation of the system-wide packages). Not all packages work when used > from outside Pkg.dir, and Pkg operations often don't see them, but you can > try and see what works vs what doesn't.
Most packages I've tested works pretty well. (Just don't expect `Pkg.*` to work). It's also usually not very hard to fix if it doesn't work. > > > On Thursday, January 14, 2016 at 9:11:20 AM UTC-8, [email protected] wrote: >> >> I work on a large compute cluster used by hundreds of university >> researchers. Our scientific applications stack is managed via RPM. I would >> like to provide users with a Julia build that: >> (1) Includes Julia base >> (2) Provides some commonly-used secondary packages - the main ones that I >> have in mind right now are the plotting packages Gadfly and PyPlot and >> perhaps also IJulia. But there may be others down the line. I want to >> provide these centrally because many, many users will want to use them and I >> want to lower the barrier to entry. I also would like to figure out the >> matplotlib dependencies in PyPlot for them so that they don't have to. >> >> The idea is to provide a base install that will be enough for many users >> (at least to get started); they can then use Pkg to add any other packages >> that they require. >> >> Is there a recommended method for centrally-installing packages like in >> (2) while also allowing users to maintain additional packages in their Home >> directories? I have not been able to track down documentation for this. >> >
