Add way to tell macports about manually installed software

[avcabob@…]

While trying to install some dependencies, macports failed, so I was able to install the dependency myself, but when I try to install what I wanted in the first place, macports still tries to install the dependency I did myself. Macports doesn't seem to notice that it's there and I can't find a way of telling it where it is. I didn't put it in a weird location or anything like that. If there is already a way of telling macports of already installed software, then explaining how to do so would be nice.

[afb@…]

Why not make a new port of the dependency, instead of installing it external to MacPorts ?

However, what would be nice would be a template - something similar to ​checkinstall

[simon@…]

You can use the bin:: or lib:: syntax to tell macports you have these files installed. Here is an extract of the macports guide (​http://geeklair.net/new_macports_guide/) how to do this:

5.2.4. Non-Port Dependencies

Port dependencies should refer to other MacPorts ports whenever possible. However, if satisfying a dependency with a port is not practical or desirable for a special reason, you may specify dependencies by having MacPorts test for an individual file by replacing port: with one of the options lib: bin: or path:.

In this lib style dependency, if the file libX11.6.x.dylib is not found in the library path the XFree86 port will be installed to satisfy it.

depends_lib         lib:libX11.6:XFree86

In this bin style dependency, if the python binary is not found in the shell's binary path the port python24 will be installed.

depends_build       bin:python:python24

In this path style dependency, if the file /usr/bin/nano is not found the nano port will be installed.

depends_run         path:/usr/bin/nano:nano

But as afb already said, it would be easier just to create a portfile for the application/library you want to install. This way you can also easier upgrade/uninstall it.

Hope this helps, Simon