I think the general (Redhat-based) scheme is to put the version after the <library>.so.# and symbolically link the <library>.so to that file, e.g.: libganglia.so.0-3.1.0 libganglia.so -> libganglia.so.0-3.1.0
That current SONAME would mean you have to link with -lganglia-3.1.0 which is pretty unusual for user-code. -Matt Chambers Bernard Li wrote: > Currently the SONAME for libganglia in trunk is: > > SONAME libganglia-3.1.0.so.0 > > Is there any particular reason why it is version specific? i.e. I > suppose this allows the user to install multiple versions of > libganglia with different versions, but is this really necessary? > > This would ultimately affect the naming of the binary package I guess: > > libganglia-3_1_0 vs just libganglia > > Thanks, > > Bernard > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Ganglia-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-developers
