Update determination of iraf and IRAFARCH variables #171
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.
These variables are now retrieved from the configuration for the different IRAF architectures instead of from
/usr/local/bin/cl
.The problems here were that
/usr/local/bin/cl
does not necessarily exist (maybeirafcl
, or at different locations)Also, there are better ways to find out the iraf variable, which are all tested here:
~/.iraf/irafroot
resp./etc/iraf/irafroot
,export iraf=/..." statement in
~/.iraf/setup.sh`,/usr/include/iraf.h
for this,/usr/lib/iraf/
,/usr/local/lib/iraf/
,/opt/iraf/
,/iraf/iraf/
and othersSimilarly, to determine IRAFARCH (if not set by environment variable):
~/.iraf/arch
(NOAO and NOIRLAB personal installations)iraf$bin.linux64
)Closes: #170