On 2015-1-24 07:22 , Jeremy Lavergne wrote: > Joshua pointed it out in a previous thread: we don't make use of other > package managers (Pip in this instance), so we shouldn't have their > packages in MacPorts unless they have requisites in MacPorts.
The opposite is equally important; i.e. something else in MacPorts requires the module. I wouldn't bother purging all the modules that don't pass this test, but I would encourage considering it before adding new ones. - Josh _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
