On Jan 25, 2008 11:55 AM, Alexander Hansen <[EMAIL PROTECTED]> wrote: > A word of caution: be careful when building packages in such cases. > You can wind up with Macports packages linking to Fink libraries, and > vice versa. This can cause problems for you down the road when you > change things via updates, removals, ...
This shouldn't be a problem in general. Each system lives in a separate part of the filesystem and keeps its own track of dependencies, so instead of cross-links what you get is multiple copies of common files such as the readline library. But an experimental/unstable (or just broken) port might have a dependency that doesn't get included as such at the package level, leaving the build-time configure script to hunt it down on its own - in that case, it might find something installed by the other system. I haven't run into this yet in practice. One way to avoid it would be to wrap the fink and port commands so they have a "clean room" shell environment, e.g. alias fink="env -i /sw/bin/fink" alias port="env -i /opt/local/bin/port" If you find that they need some environment variables set, you can add them, e.g. alias port="env -i LD_LIBRARY_PATH=/opt/local/lib /opt/local/bin/port" but so far that doesn't seem to be necessary. -- Mark J. Reed <[EMAIL PROTECTED]> ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
