NOIRLAB: zzsetenv.def updates #365
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
olebole
force-pushed
the
noirlab-zzsetenv
branch
from
943ea3e to
0ccd137
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change from the NOIRLAB IRAF code updates come configuration in zzsetenv.def, mainly:
clobber=yeszzsetenv.deflocally in${HOME}/.irafhlib$extern.pkgoptionalOriginal commits:
7d5b420 - reset clobber=yes as default
59a1489 - allow local definitions in iraf$extern and home$.irafca7fcf3 - add alt sources of pkg defs
9125745 - make zzsetenv.def in some locations optionalThe second commit removed the conditions, and the leading spaces in the set statement, because this is buggy in NOIRLAB IRAF. Because the community version doesn`t have this problem, this is omitted here.
The fourth commit was a hack that allowed to have the file optional at the hardcoded locations
iraf$externandhome$, which is not required in the community IRAF code (#270).@mjfitzpatrick, why don't you take over the code from the IRAF community here?