On Wed, Nov 30, 2011 at 02:49:57AM -0500, KonaBlend wrote: > 1. new port:mkvtoolnix-gcc46 and install to mkvtoolnix private subtree. > 2. new port:mkvtoolnix-boost and install to mkvtoolnix private subtree. > 3. modify port:mkvtoolnix to depend on port:mkvtoolnix-gcc46 and > port:mkvtoolnix-boost and install to mkvtoolnix private subtree. > 4. make mkv executables available to /opt/local/bin via symlinks
This solution seems like overkill, but maybe that's because I'm not understanding the problem correctly. Have you run into specific issues with the existing boost and gcc46? (...aside from gcc46 currently being broken, as we've discussed elsewhere) I can see why you might want to avoid linking a clang-built boost against a gcc46-built mkvtoolnix, but why do you think a separate gcc46 port is necessary? Does mkvtoolnix need something that isn't provided by our existing gcc46 port? More generally, I wonder if there are issues here that other ports will need to address, and if so whether we can come up with a common solution. Dan -- Dan R. K. Ports MIT CSAIL http://drkp.net/ _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
