Continuing the discussion from Possible documentation errors:
Yes, I’d love to work on some practical EUPS-for-LSST documentation this summer.
On the reference side, yes, we do need to list tags. Otherwise I think we send people to an EUPS server URL to find tags, which isn’t an ideal solution. We also need to list what top-level packages are available, and why someone might install one or another (see also RFC-305, which seeks to more clearly define their roles).
We also want some EUPS overview documentation (define basic terminology, like tags versus versions, and the philosophy of EUPS in general).
But I think the core of the EUPS-for-LSST documentation should be short how-to recipes for dealing with certain situations.
So I’d like us ot use this thread to write down what things we do with EUPS, and how we identify and work-around issues. I’ll use the results as research material to put together an EUPS how-to for piplines.lsst.io.
To kick things off, some basic tasks are:
- Installing a package,
eups distrib install ...
- Setting up a package (and all variations on setting up specific tags, and the
- Creating tags,
- Listing installed packages,
- Listing installed versions of a package,
eups list -v packages
- Listing set up packages,
eups list -s
This is just a cursory beginning. If others from DM and Sims want to write down your common EUPS tasks, that’d be fantastic.