Per discussion on the teleconf today, since the only OMPI member who
cares has a workaround in their packaging of Open MPI for library
versioning (Sun / ClusterTools), we have dropped this issue. When/if
someone cares about it enough in the future, they can re-open the
issue. I have filed
Christian Bell wrote:
> On Mon, 15 Oct 2007, Brian Barrett wrote:
>
>> No! :)
>>
>> It would be good for everyone to read the Libtool documentation to
>> see why versioning on the release number would be a really bad idea.
>> Then comment. But my opinion would be that you should change b
BTW, Here's the documentation I was referring to:
http://www.gnu.org/software/libtool/manual.html#Versioning
Now, the problem Open MPI faces is that while our MPI interface
rarely changes (and almost never in a backwards-incompatible way),
the interface between components and libraries do
Ok, having read the libtool docs now, I see why the release number is
a bad idea. :-)
I'm assuming that:
- The libmpi interface will rarely change, but we may add to it over
time (there's a specific point about this in the libtool docs -- no
problem)
- The libopen-rte interface historica
Christian Bell wrote:
On Mon, 15 Oct 2007, Brian Barrett wrote:
No! :)
It would be good for everyone to read the Libtool documentation to
see why versioning on the release number would be a really bad idea.
Then comment. But my opinion would be that you should change based
on in
On Mon, 15 Oct 2007, Brian Barrett wrote:
> No! :)
>
> It would be good for everyone to read the Libtool documentation to
> see why versioning on the release number would be a really bad idea.
> Then comment. But my opinion would be that you should change based
> on interface changes,
No! :)
It would be good for everyone to read the Libtool documentation to
see why versioning on the release number would be a really bad idea.
Then comment. But my opinion would be that you should change based
on interface changes, not based on release numbers.
Brian
On Oct 15, 20
WHAT: Add versioning to all OMPI libraries so that shared libraries
use the real version number in the filename (vs. the current "*.so.
0.0.0")
WHY: It's a Good Thing(tm) to do.
WHERE: Minor changes in a few Makefile.am's; probably some small
tweaking to top-level configure.ac and/or some s