[Lsb-infrastructure] libtodb2 questions

Denis Silakov silakov at ispras.ru
Tue Jul 15 01:10:43 PDT 2008


Hi, Ron,

To say the truth, libnss is not a good starting point to become 
acquainted with library upload process. First, the symbols listed in 
wiki (http://www.linuxfoundation.org/en/NssPublicFunctions) actually 
come from two libraries - libnss3 and libssl3. Furthermore, these 
functions use headers from /usr/include/nss3 and /usr/include/nspr4 
folders; the latter formally belongs to the libnspr4 library (not going 
to be included in LSB), so we should carefully separate libnspr4 stuff 
from libnss3 and libssl3 elements.

However, there is no need for you to bother about uploading libnss data. 
The thing is that we also recently took a look at NSS functions as a 
good trial for libtodb2 and we already have (almost) working data. And 
we are actually planning to update libtodb2 on the basis of our 
experiments to simplify the upload process and to introduce an 
alternative way of data collection - using gcc and headers instead of 
readelf and debug information.

I'll put necessary NSS data to the bug 2222 
(http://bugs.linuxbase.org/show_bug.cgi?id=2222). Hope we'll be able to 
upload libnss3 and libssl3 to the devel db in a week or so.

As for your question about ArchLib entry, it's a known bug - neither the 
tool creates a record nor documentation says to create it manually; this 
will be fixed in the updated tool.

To create this entry, the following queries can be performed:

SET @Lid=(SELECT Lid FROM Library WHERE Lname='libnss3');
INSERT INTO ArchLib VALUES( @Lid, 1, 'libnss3.so', '4.0', NULL );

(Note that it would be more correct to call the library 'libnss3', 
especially keeping in mind accompanying 'libssl3' which should not lead 
to confusion with libssl coming from openSSL).

-- 
Regards,
Denis.



More information about the lsb-infrastructure mailing list