Details
-
Type:
Improvement
-
Status: Invalid
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: Developer Infrastructure
-
Labels:None
-
Team:SQuaRE
Description
Why does newinstall.sh need to install the lsst package?
From a discussion in the dm-square Slack room:
Tim Jenness [1:03 PM]
but please explain why `lsst` should be installed
John Swinbank [1:05 PM]
(I don’t know where that question was directed, but for what it’s worth I have no idea: it seems unnecessary to me.)
(But if it’s going to be done, we should at least do it correctly.)
Tim Jenness [1:06 PM]
I was asking the ether for inspiration.
it seems to serve no purpose to me other than to confuse things
for example, it insists on installing sconsUtils and that breaks if you have an old compiler (edited)
Fritz Mueller [1:07 PM]
successfully confused me (edited)
Tim Jenness [1:07 PM]
even if you aren’t even wanting to build any C++ code with your eups distrib install
Jim Bosch [1:08 PM]
Our pure-python packages require sconsUtils too.
Tim Jenness [1:08 PM]
but the third parties don't
it seems premature
Jim Bosch [1:08 PM]
Agreed.
It seems to be a metapackage that has lost its purpose. (edited)
Attachments
Issue Links
Activity
Field | Original Value | New Value |
---|---|---|
Component/s | Developer Infrastructure [ 10712 ] |
Priority | Major [ 3 ] | Minor [ 4 ] |
Resolution | Done [ 10000 ] | |
Status | To Do [ 10001 ] | Invalid [ 11005 ] |
It seems that the main purpose of the lsst package is to set some environment variables. These variables seem to be known to the newinstall.sh script itself and can therefore be burned in to the loadLSST scripts that are created. This would remove the need for the lsst package to be installed.