Rainer Müller wrote: > Joshua Root wrote: >> Was a ticket ever filed for this? I gather that the problem is that >> activation doesn't follow directory symlinks - I wonder if making it >> do so would break anything? > > Symlinks are owned by a specific port, directories are not. > > So if we follow the symlinks, stuff will end up at places it was not > meant to be.
If I'm understanding correctly, stuff installed by the affected py-* ports would end up where it *is* meant to be. No? > If the port owning the symlink is deactivated/uninstalled, > other ports could break as they are probably expecting stuff under the > symlink. Could be a problem in some cases, but python modules already break by definition if you remove python. > This wouldn't be a good idea. But we could need a better error message > than what we currently have. > > Rainer - Josh _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev