[ofa-general] Re: Dapl 2 question/issue

[Doug Ledford]

On Tue, 2008-01-29 at 10:44 -0800, Arlin Davis wrote:
> Doug Ledford wrote:
> > OK, I've been working on integrating the latest dapl stuff into our
> > RHEL5.2 product and I've come across what I think is an issue.
> > 
> > The dapl-2 code is not compatible with dapl-1 code, and there is a
> > (albeit small, but still it exists) amount of work to forward port code.
> > However, you maintained the same library name (aka, libdat) for both
> > dapl-1 and dapl-2.  
> 
> Yes, I wanted to stay away from renaming on every major release if 
> possible. But I can see your point if someone wants v1 and v2 
> development packages on the same system. The intention was to provide 
> only the latest development environment with older versions supported in 
> libraries only.

Well, let me say why I bring this up.  Although I don't personally know
anyone that uses it this way, our openmpi package is built with udapl
provider support.  So, here I am getting ready to build openmpi-1.2.5,
and I would have to turn off the udapl provider if I didn't include the
dat-1 devel environment because openmpi has not been forward ported (to
my knowledge, but the fact that is still uses #include <dat/dat.h>
instead of #include <dat2/dat.h> is a strong indicator).  If I turn of
the udapl provider to openmpi is probably isn't any big loss since most
people in their right mind just use the openib provider instead.  But,
technically, it would be a regression since it was enabled previously.
So, this is the sort of thing I ran into.  I figure if it effects me, it
just might bite some user out there too.  Hence this conversation.

> That means that, if code were to #include
> > <dat/dat.h> and then link against -ldat, they would get the old dapl-1
> > headers and the new dapl-2 library (assuming the dapl-1 headers are
> > installed, which realistically they need to be until all dependent code
> > has been forward ported to dapl-2).  In order for dapl-1 and dapl-2
> > libraries and devel environments to be installed simultaneously, which
> > is what you need for a seamless migration from version 1 to 2, you need
> > different names on the libs.  Is there any chance we can get an updated
> > dapl-2 that actually changes the lib name to libdat2.so instead of just
> > libdat.so?
> 
> I have no objections to libdat2.so.
> 
> James, do you see any issues? Anyone else?
> 
> -arlin
> 
-- 
Doug Ledford <dledford at redhat.com>
              GPG KeyID: CFBFF194
              http://people.redhat.com/dledford

Infiniband specific RPMs available at
              http://people.redhat.com/dledford/Infiniband
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.openfabrics.org/pipermail/general/attachments/20080129/cd1da96a/attachment.sig>