Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DM-6316: Add option to allow miniconda3 to be installed #27

Merged
merged 3 commits into from Sep 7, 2016

Conversation

timj
Copy link
Member

@timj timj commented Sep 1, 2016

No description provided.

@@ -282,11 +306,18 @@ set -e
########## Download optional component (python, git, ...)

if true; then
if [[ $WITH_MINICONDA2 = 1 ]]; then
Copy link
Member Author

@timj timj Sep 2, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The single = here looked inconsistent so I changed that to ==.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm confused. sh uses = not ==.

I don't think [[ ... ]] is in posix:

The following words may be recognized as reserved words on some implementations (when none of the characters are quoted), causing unspecified results:
[[ ]] function select

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This script is actually documented to be a bash script and not a sh script (see the installation instructions: https://pipelines.lsst.io/install/newinstall.html ) so I don't think there is a problem.

@timj
Copy link
Member Author

timj commented Sep 2, 2016

I've cleaned up the tab issues.

else
if [[ $PYVEROK != 1 ]]; then
cat <<-EOF

LSST stack requires Python 2.7; you seem to have $(python -V 2>&1) on your
LSST stack requires Python 2.7 or >=3.5; you seem to have $(python -V 2>&1) on your
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we're going to allow a (nonexistent) 2.8 in the code, shouldn't you put a ">=" on the 2.7, too?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So long as that does not confuse people into thinking 3.1 is okay.

@timj timj merged commit 32aa4ec into master Sep 7, 2016
@ktlim ktlim deleted the tickets/DM-6316 branch August 25, 2018 06:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants