Created attachment 335626 [details] pyraf ebuild Hi! I am Anurg Garg, from India. I am Physics teacher and amatuer astronomer. I am also Free Software hobbist and contributor (Hindi Transtor in Gnome and Hindi Translation coordinator for Xfce). For me IRAF and its python module pyraf is one of the most import programs available in image processing. I first started with the ebuild for IRAF, but my lack of experience in ebuild programing and IRAF's non-conventional way of installation (using csh bsed script as installation medium and non-availability of makefiles) made it hell difficult for me to got it done. So, I installled IRAF by hand and moved to ebuild for Pyraf. Please find attached pyraf-2.0.ebuild so that it will compile against python-2.7 Its essential dependency stsci-tools will be submitted as a saparate bug. PyRAF is a command language for running IRAF tasks that is based on the Python scripting language. It gives users the ability to run IRAF tasks in an environment that has all the power and flexibility of Python. PyRAF can be installed along with an existing IRAF installation; users can then choose to run either PyRAF or the IRAF CL. PyRAF is part of the stsci_python package of astronomical data analysis tools, and is a product of the Science Software Branch at the Space Telescope Science Institute. The current release of PyRAF is v2.0 and can be downloaded from the stand-alone PyRAF download page - http://www.stsci.edu/institute/software_hardware/pyraf. I suggest sci-astronomy/pyraf.
Created attachment 335628 [details] Stsci-tools ebuild. it is dependency for pyraf Please find attached stsci-tools-2.0.ebuild so that pyraf compile against python-2.7 It is a essential dependency for pyraf installation and it is provided with the source code of pyraf, and do not have saparate independent installation source code. In the ebuild name of the stsci-tools I've used a version number 2.0, just to be consistent with the naming convention and there is no version satisfied for this program. It is provided along with pyraf-2.0 and has to be installed prior to pyraf. Also, I could not handle installation of both the programs from one ebuild (which would be more suitable way of installing, as both comes from same source code), hence formed to different ebuilds for both and added stsci-tools as dependency in pyraf ebuild. Any help suggestion in this regard is most welcome.
> # Copyright 1999-2012 Gentoo Foundation You can use 2013 now, the header for new ebuilds should be the same as the skel.ebuild file in Portage. > EAPI=4 EAPI=5 has recently became stable. > LICENSE="BSD Similar" There is no "Similar" license in the licenses directory of Portage. > KEYWORDS="amd64 ~x86 ~x86-fbsd ~amd64-linux ~x86-linux" Packages need to be unstable for some time before you can consider them stable, otherwise you have the risk of breaking the system of a large amount of users if something goes wrong... >src_compile() { > cd "${S}" > distutils_src_compile >} You can leave out this function since distutils' src_compile will do this by default as you inherit it.
Created attachment 335822 [details] pyraf ebuild (with suggested changes)
Created attachment 335824 [details] Stsci-tools ebuild. it is dependency for pyraf (with suggested changes) I am attaching stsci-tools ebuild with suggested changes. Kindly find it with in the atachment
it could be very useful, unfortunately i think it should depend on iraf, which is not in the tree, and is quite a beast to do an ebuild.
