Ticket #14796 (pike): please commit
peter at pogma.com
Wed Apr 2 17:43:58 PDT 2008
Jordan K. Hubbard wrote:
> I think we must be talking about a different mechanism since in what I'm
> suggesting, the embedded paths WOULD point to the appropriate depot
> locations, the install_name of the libs WOULD be the target locations
> and applications absolutely WOULD look for their resources in the depot
> locations. There are no technical reasons why this wouldn't be possible
> and, as someone else recently pointed out, the GoboLinux* folks have
> certainly managed to do it.
We do it at work (thewrittenword.com) too. For the default customer,
packages are installed to /opt/TWWfsw/<pkgname><version>. e.g. libpng is
installed to the /opt/TWWfsw/libpng12 prefix (for libpng-1.2.x),
gcc-4.2.2 is installed at /opt/TWWfsw/gcc42 and so on.
There is really little point in having libpng1218 libpng1219 etc as they
are ABI compatible. If we had fully versioned library install locations
like that, we could not update the libpng version for security fixes
without rebuilding everything that uses it too.
It certainly works, but we have to patch the majority of packages to get
them to work like that. And to build some packages you end up with a
very long list of things in PKG_CONFIG_PATH LDFLAGS and CPPFLAGS.
More information about the macports-dev