On Tuesday January 20 2015 12:25:32 Michael Dickens wrote: > but that's ugly & cumbersome. There has got to be a better way. Any > advice on a robust yet concise way to do this? Thanks! - MLD
Hi Michael, 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? 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. R. _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
