Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-12028

newinstall.sh should not set PATH unless miniconda is bootstraped

    Details

    • Templates:
    • Story Points:
      0.5
    • Epic Link:
    • Team:
      SQuaRE

      Description

      Craig Loomis [10:40 AM] 
      A fresh `https://raw.githubusercontent.com/lsst/lsst/master/scripts/newinstall.sh`, run without installing a miniconda, generates a loadLSST.bash which contains a troublesome `export PATH="/bin:${PATH}"`. Not entirely sure what is supposed to be happening with the `miniconda_path`, etc. variables in the use-user-anaconda case. MacOS 10.12, anaconda 4.4.0.
       
       
      Tim Jenness
      [10:42 AM] 
      @josh  I think you need to protect `export PATH="${miniconda_path}/bin:${PATH}"` so that it only happens if we installed miniconda. (edited)
       
       
      [10:43] 
      actually it’s this line sorry:
      ```local cmd_setup_miniconda="export PATH=\"${miniconda_path}/bin:\${PATH}\""```
      

        Attachments

          Container Issues

            Activity

              People

              • Assignee:
                jhoblitt Joshua Hoblitt
                Reporter:
                jhoblitt Joshua Hoblitt
                Reviewers:
                Tim Jenness
                Watchers:
                Joshua Hoblitt, Tim Jenness
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Summary Panel