GammaLib

Great. Indeed, ultimately I would like to have GammaLib installed through all available package managers. This is one of the items we have on our task list. If you can take about MacPorts, this would be great.

Can you put information about the procedure somewhere in the Wiki? We may generate a new page called “deployment”, under which we will then create pages for the various systems.

By the way: if you have written a script for deployment it can go in the dev directory of GammaLib, where I gather actually scripts used for various development issues.

For the MacPorts version, I guess we want to create the SWIG wrappers so that SWIG is not needed for deployment. In dev there is a script called release_gammalib.sh which I use for release. This script creates the Python wrappers and PDF files for documentation before making a tarball. That’s the tarball that I then put on sourceforge.

Christoph Deil wrote:

Jürgen Knödlseder wrote:

Great. Indeed, ultimately I would like to have GammaLib installed through all available package managers. This is one of the items we have on our task list. If you can take about MacPorts, this would be great.

Can you put information about the procedure somewhere in the Wiki? We may generate a new page called “deployment”, under which we will then create pages for the various systems.

I don’t see any buttons to edit the wiki /create new pages. Do I need extra permissions?

It took me some time to find this one out:

Just add My new page somewhere where you want to add a link to the new page (we may add a page Deployment to the Sidebar, can be edited by clicking on sidebar on the right panel). You then get a red link. Click on it and the page will be created.

By the way: if you have written a script for deployment it can go in the dev directory of GammaLib, where I gather actually scripts used for various development issues.

For Macports all that is needed is one Portfile which will live in the macports repo. Based on the instructions in that file, Macports then fetches the standard gammalib tarball from sourceforge and builds / installs it. To illustrate I have attached the preliminary version of the Portfile, it is work in progress.

Thanks. Would it make sense to have this Portfile in the dev folder? This would give us version control over this file.

For the MacPorts version, I guess we want to create the SWIG wrappers so that SWIG is not needed for deployment. In dev there is a script called release_gammalib.sh which I use for release. This script creates the Python wrappers and PDF files for documentation before making a tarball. That’s the tarball that I then put on sourceforge.

I could specify in the Portfile that the gammalib configure is passed the option not to recreate the SWIG wrappers even if swig is available. But installing swig and making it a gammalib dependency would also be trivial with Macports. As you like.

This is done already by GammaLib. It checks if the SWIG wrapper files are available, and if all are present, it skips the SWIG step.

I think it’s always better to reduce the dependencies

As you see above, red links are even created when you type in the issue comments

Jürgen Knödlseder wrote:

Christoph Deil wrote:

Jürgen Knödlseder wrote:

Thanks. Would it make sense to have this Portfile in the dev folder? This would give us version control over this file.

I don’t think we should keep the Portfile in the gammalib repo. The right place is the macports SVN repo where all Portfiles live. We can add a link to the Portfile from the Deployment wiki page. Here’s an example for the cfitsio port:

https://trac.macports.org/browser/trunk/dports/science/cfitsio/Portfile