On Tue, Aug 12, 2008 at 02:41:29PM +0100, Kostas Georgiou wrote: > On Tue, Aug 12, 2008 at 07:38:15AM -0500, Martin Hicks wrote: > > The common practice in the rpm world is to not to use the soname for the > latest version and have something like compat-ganglia-30 or libganglia30 > for example for the older versions (no need to encode the minor version > since changes there don't break compatibility).
well, a little known ganglia secret is that before 3.1.0 everything was linked statically to libganglia and so the "so" was never used, at least internally and we just hoped no one did externally (indeed applications that we even host together with ganglia, like gexec were knowingly broken) before 3.1.0 there wasn't even a public interface (as defined by a set of headers that export a stable ABI) and therefore there was a high possibility it could break even with minor version changes and so using a different library package for each release helps protect someone that relied on what they though was a public interface and linked against it. with 3.1.0 we started finally using it and even did some attempt to define a public interface to it through public headers (really forced to us because of the need to be able to compile DSO outside the ganglia tree), but the soname is 0.0.0 and there has not been yet formally any warranty that it won't break in the future (mainly because we only massaged a little so it worked for us for most cases). Carlo ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
