On Jan 3, 2007, at 1:20 PM, Adam Fedor wrote:
On Jan 3, 2007, at 10:15 AM, Larry Campbell wrote:
Yes, but if one component wants to use a new version and nineteen
others don't care, the nineteen others still have to relink if
they're to be deployed along with the one. It's the relinking of
the nineteen others that's the killer.
You should be able to install several versions of the GNUstep
libraries at once, unless you are installing from a distribution
that does not allow that. Applications should use the old version
unless they are specifically recompiled. It's possible this could
be a problem since Resources aren't versioned, but it's not likely.
This is a problem for us because we deploy tarballs of binaries, and
the tool chain that builds & deploys the tarballs complains if there
are duplicate files. We could probably do some huge hack to allow it
to work, but it sure would be simpler if gnustep-base wouldn't
require binding to the minor version.
Apple certainly doesn't make you relink everything whenever a new
version of MacOS X comes out!
_______________________________________________
Discuss-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/discuss-gnustep
