Well presumably it could do something that the import logic already does, but I appreciate that it is complex logic.
David: @wildart is the person to follow for the future of package management. On Mon, Jun 27, 2016 at 2:02 PM, Stefan Karpinski <[email protected]> wrote: > You can use LOAD_PATH to look in a stack of directories, and you can even > set ENV["JULIA_PKGDIR"] to change which one Pkg manages, but you cannot > manage more than one of them at the same time, since it's unclear what this > would even do. > > On Mon, Jun 27, 2016 at 1:28 PM, David Parks <[email protected]> > wrote: > >> I want to set up a specific Julia environment on a cluster for other >> people to use. I have particular packages, including some that are dev >> branches, and even some that draw from my own fork of a branch to support a >> custom feature for this environment. So the package setup is non trivial >> and I don't want everyone else to have to follow the details. >> >> Is there a way (now or in the future) to have a hierarchy of package >> directories, so I could have a main repository that I setup and control for >> the relevant packages, but still allow users to extend on that but into >> their own package directory? >> >> Or is there a way good way for me to auto-configure a complex package >> directory for the user? I suppose the obvious answer is to just write a >> package setup script, which might be a suitable solution. But I wonder if >> anything else is possible or on the horizon. >> >> Thanks, >> David >> >> >
