Removing a port

Lawrence Velázquez larryv at
Thu Apr 4 12:10:46 PDT 2013

On Apr 4, 2013, at 8:34 AM, Thomas Robitaille <thomas.robitaille at> 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?


More information about the macports-dev mailing list