On Tue, Jan 20, 2015, at 02:26 PM, René J.V. Bertin wrote: > I suppose you're not supporting any random swig version, so how about > doing what the python Portfile itself does, a foreach over a list of > known versions? swig-python and swig-python-devel both don't install a > single common file?
I could create a PortGroup called swig-1.0 which handles this: yes, that is true. Not pretty, but it could work. I'd prefer to not have to do this, given the number of ports that use SWIG (something like 82, from a quick search). Maybe this is actually the better way to go ... have to think about this. > Alternatively someone could implement stub or virtual ports, if they > don't exist already, a feature by which port:swig-python-devel itself can > signal that it provides port:swig-python, rather than leaving it up to > client code to figure out if something equivalent to port:swig-python is > installed. Nope; no that way. - MLD _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
