Details
-
Type:
Bug
-
Status: Invalid
-
Resolution: Done
-
Fix Version/s: 8.0.1
-
Component/s: Developer Infrastructure
-
Labels:
-
Team:Architecture
Description
I installed a clean Winter2014 on my Mac in a new directory using the standard procedure (from a fresh login; my old stack was NOT setup):
mkdir lsst_home2
|
cd lsst_home2
|
curl -O http://sw.lsstcorp.org/eupspkg/newinstall.sh
|
bash newinstall.sh
|
It completed without errors, but when I tried to setup some packages it complained that it could not find suitable versions. It turned out that many packages in my new stack were missing the "current" tag. Those packages all had one thing in common: I had a git version checked out and declared in my old stack using version name "git" and tag "rowen" (my username). Many, perhaps all, of those git packages were also tagged "current" in my old stack.
I have no idea how my new stack could have learned anything about packages declared in the old stack. The only LSST environment variables that I normally have defined are $LSST_HOME and $LSST_GIT, and I'm pretty sure I updated the former for the new stack before starting the installation.
Neither my old or new stack has a developer sandbox (since it is on my personal work computer).
My `.eups/startup.py` contains just one line:
hooks.config.Eups.userTags += ["test"]
|
and I do not actually use that tag anymore (I always use "rowen", instead) so I should probably comment that out.
Attachments
Issue Links
- mentioned in
-
Page Loading...
Activity
Hmm, OK, I understand; what you're saying is that 'current' is not necessarily the default tag to be used by setup, that one can override it via hooks.config.Eups.defaultTags?
OK... Let's imagine I override the default and make 'beta' the default tag. Does that mean that eups distrib install foo will look into beta.list to find the version of product foo?
Is this ticket still relevant?
Kian-Tat Lim / Gabriele Comoretto [X] can we shut this ticket down?
eups is, as discussed above, behaving as designed. The current tag should be explicitly assigned if desired.
Yes, that should be the default assumption. I know it's not as default as it once was (given laptops), but it's much the most efficient way to work.
So we coordinate global tags between sites, and current is indeed a sort of global tag — it's the default global tag. I do not think that we should manage what a given site thinks of as current; we do manage beta and HSC and ... and if that matters they should use setup -T beta (or make beta a default post-tag via hooks.config.Eups.defaultTags["pre"].append("beta") which essentially replaces "current" by "beta" as the default global tag