Hi DM experts,
As a new user, I am facing a situation where I’ve been pointed to centrally managed versions of the DM stack where I don’t have write access (e.g., weeklies at Lyon or installs at SLAC). I’ve been facing the situation where there are packages that I need that are not installed centrally (the most important example being
lsst_sims). If I were pointing at my own version of the stack I would solve this problem with a
eups distrib install; however, on centrally managed stacks I generally do not have write access. I’ve faced a similar problem before in other non-lsst environments, I’ve been able to cobble together a solution by installing my own version
eups, prepending its path to my
$EUPS_PATH, and using the
--nolocks --no-server-tags options for
eups distrib install.
So far, I haven’t been able to get a similar solution working with the DM stack. I was wondering if anyone else had solved the problem of installing on top of write-protected central installs.
Tagging @johannct, @heather999, @ljones, and @rhl since we’ve started to discuss this on slack.