Similar to what happened yesterday evening in OMPI, I introduced
explicit libplpa.so versioning on the PLPA SVN trunk and v1.3 branch.
See
http://www.open-mpi.org/community/lists/devel/2009/07/6522.php for a
post on the OMPI devel list that includes 3 pages from the GNU Libtool
2.2.6a documentation explaining the process. It's the Right Thing to
do.
It's a fairly trivial change to a Makefile.am to explicitly state what
version number we want libplpa.so file to have. This only has effect
on standalone PLPA builds; embedded builds don't bother with a shared
library version number. Note, too, that this version number is *only*
meaningful in actual PLPA releases. Hence, the intent is that the
version number will remain 0:0:0 on the SVN trunk (and any derived
developer branches). The version number will change immediately prior
to a release on release branches only.
We'll bootstrap the versioning process by knowing that PLPA v1.3 was
released with version 0:0:0. The next release (whether it's 1.3.1 or
1.4) will update the version numbers as appropriate.
--
Jeff Squyres
jsquyres_at_[hidden]
|
![[Flag]](../../../../../community/mirrors/flag-us.gif){kind=small}