Details
-
Type:
Story
-
Status: Won't Fix
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: lsstsw
-
Labels:None
-
Story Points:5
-
Team:SQuaRE
Description
To reduce disk usage, it is very handy to be able to make build/afwdata and stack/afwdata/BLAH be symlinks. build/ is easy: just make the symlink and then never have touch it unless you rm your whole stack. stack/afwdata/BLAH is harder: each time you rebuild something that depends on afwdata, it will install a new copy of afwdata, which you'll have to manually remove and declare your symlink with a new tag.
A couple of ways to make this more automatic:
- lsstsw checks whether build/afwdata is a symlink, and if so just makes the new stack "install" a symlink to the same directory.
- Check for some environment variable (e.g. AFWDATA_BASE_DIR or something) and if that exists, just make a symlink to it, or make a dummy eups table that points to that directory and don't put anything in stack at all.
Attachments
Issue Links
- relates to
-
- Done
Activity
Thanks John Parejko; this is wonderful. I have added a Python version which requires defining two env variables
Given that the big problem with afwdata installing multiple times has been fixed by DM-22305 (it no longer depends on sconsUtils so will only be reinstalled when it changes) I suggest we close this ticket as Won't Fix.
I've tweaked my bash script version so that it doesn't muck up the new conda environment and does the symlinking in the right place.
Marking this won't fix, as there are a couple of scripts that take care of the symlinking for those that need it, and dependencies on big packages have been trimmed down.
I've attached a short bash script that does the cleaning up. Modify the two directories at the top as appropriate, and run it after you rebuild lsstsw, and it will remove any new testdata directories and replace them with symlinks, in a way that I believe to be fairly safe.