So, I dropped the ball - the January 14 2008 critical update to IRAF? I never bothered to incorporated the updated binaries to my .pkg installer. I have done so now, and the installer for IRAF 2.14 on the download page contains the updated binaries.
This is also the first time I’ve used Packagemaker in xcode 3.0, so … I now am requiring authorization to install and I think I have it set up so that the iraf user will be given ownership, but I’m not 100% sure that’s going to work. Let me know if there are any problems.
Oh, and as an aside - did you see the iPhone version of IRAF?. Quite amusing.
Share This
Tags: installers, intel, IRAF, pkg — .
IRAF 2.14 has been announced and is available for download. The Mac (PPC and Intel) versions appear to work properly on both Leopard and Tiger. I’ll try and have installers made for these today. Certainly, I can test the Intel one easily but it’s harder for me to test the PowerPC version so once it’s up if someone out there could test it, that’d be appreciated.
Update The Intel installer is available here - Download IRAF 2.14 for Intel Macs .pkg installer (57MB). My prescribed update method is simple. Change to the IRAF user and do:
% cd /
% mv iraf iraf_old
Run the installer and then:
% mv /iraf_old/extern /iraf/extern/
That should preserve all your external packages. You will most likely want to copy over the extern.pkg from your old install.
% cd /iraf_old/iraf/unix/hlib
% cp extern.pkg /iraf/iraf/unix/hlib/extern.pkg
That should work. Let me know if there are any problems - it worked ok for me. I’d keep /iraf_old around for a while just to be safe. And remember any installer errors are probably permission issues but be sure to check the log first before emailing me with any problems.
Share This
Tags: 2.14, installers, IRAF, iraf.net, Leopard, Tiger, unix — .
A common problem with the IRAF installers is that / is sometimes not writeable by the admin group, and thus the “iraf user” can’t write files to the root of the hard drive. To see what goes wrong with the installer, please check the installer log. You can see a screenshot here.
If it’s something about permissions, making / writeable by the admin will probably fix it (assuming IRAF is an admin user, as I suggest)
sudo chmod g+w /
Share This
Tags: installers, IRAF, permissions — .
The way I make this work is to change the editor defined in the login.cl file from vi to emacs. The cl uses keybindings based on the editor and for whatever reason, changing the editor to emacs does the trick. You have to remove the comment # from the set editor line and then change it to emacs so it then looks like
set editor = emacs
Now, I personally never have IRAF invoke the editor defined in my login.cl file so this change has no effect for me other than making the delete key work. I’m not really sure when the editor is the login.cl file is used. But presumably this change would force you to use emacs when you want vi.
Share This
.
Well, the download page was rather confusing collection of links, and had the Intel installers rather hard to find sometimes, so I reorganized it a bit today. Hopefully, it’ll be less confusing now.
Share This
.
So, this bug may cause a “bus error” when using display to show certain float images. There is a fix described in the thread, and I have incorporated the fixed binaries now into the IRAF installer, which you can find on the download page as always.
Share This
.
This may be common knowledge among some IRAF users, but I came across this in the IRAF.net forums and its news to me. You can make shell scripts that call the CL, to use IRAF tasks from outside of IRAF. Check out the details here.
Share This
.
