Removing a port

[Ryan Schmidt]

On Apr 10, 2013, at 15:30, Thomas Robitaille wrote:
> On 4 April 2013 21:10, Lawrence Velázquez wrote:
>> On Apr 4, 2013, at 8:34 AM, Thomas Robitaille wrote:
>> 
>>> Obviously, it'd be great if it could be fixed, and I tried fixing it
>>> before, but it's all quite complicated - the issue is that the tar
>>> ball includes some dependencies, so those should really be removed,
>>> and the Makefile would need to be re-written to allow the custom
>>> compiler and linking path, etc. The package doesn't follow the
>>> standard 'configure' method for linux packages, which complicates
>>> things further. Development is not very active, which means that it's
>>> not easy to submit a patch upstream. On the other hand, the only
>>> important part of the package is a bunch of C files, so maybe there's
>>> a way to essentially create a new tar file that has a configure script
>>> and uses MacPorts for the dependencies. If someone would like to help
>>> with this, then I would be very grateful, but otherwise, I will likely
>>> have to remove the port.
>> 
>> Which port is it?
> 
> It's called 'montage':
> 
> $ port info montage
> montage @3.3, Revision 3 (science)
> 
> Description:          Montage is a toolkit for assembling Flexible Image
>                      Transport System (FITS) images into custom mosaics
> Homepage:             http://montage.ipac.caltech.edu/
> 
> Library Dependencies: jpeg, cfitsio
> Platforms:            darwin
> License:              http://montage.ipac.caltech.edu/docs/download.html
> Maintainers:          robitaille at macports.org

It looks like getting it to use the right compiler is fairly straightforward, using the usual method detailed in the wiki:

https://trac.macports.org/wiki/UsingTheRightCompiler

But there are some other issues too.