On 2012-5-21 05:33 , Jeremy Lavergne wrote: >> They just keep coming back, which isn't too surprising for something >> with "cache" in its name... > > So the port really needs to make sure it nukes those in post-destroot, right?
That would be one solution to stop the conflicts, but then the .pyc files would be left behind when the port is uninstalled. It looks like at least some distros are instead ensuring that they *do* install them, since python 3.2 will generate them at runtime if you don't. - Josh _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
