[Pkg-libburnia-devel] Symbols files

George Danchev danchev at spnet.net
Tue Apr 5 12:12:23 UTC 2011


On Tuesday 05 April 2011 11:43:43 Simon Huggins wrote:
> Salut George !

Bonjour Simon!

(thanks for the ping, bouncing that to the list now)

> > Symbol files are now removed because we do control the exported
> > symbols upstream via link script, see the *.ver files in source trees,
> > thus I decided that maintaining another level of symbols checks would
> > be redundant, and waste of time. If you share a different view, please
> > let me know.
> 
> Are .ver files enough for dpkg-shlibdeps to do the right thing?

Actually dpkg-shlibdeps does not look at these linker script file, i.e. *.ver 
files in our case.

> i.e. it won't always try and link to the latest verison of the lib it'll
> try and link to the version that has that symbol but no later?

I must admit that, having maintaining a track in which particular version a 
given symbol has been introduced, is a compelling reason to resurrect the 
symbol files support once again, this would help build rdeps. 

OTOH, there used to be some private symbols leaked with our former set of 
symbols file (a great part due to my own fault), but now with the linker script 
introduced upstream few months ago, we can have the symbol files well sorted 
out.

> I've been away from this for a while but from
> http://wiki.debian.org/Projects/ImprovedDpkgShlibdeps it seems to
> suggest that you might need to provide a mapping between the versioned
> symbols and the version of the package.

I'll have a look once again at that too.

-- 
pub 4096R/0E4BD0AB <people.fccf.net/danchev/key pgp.mit.edu>



More information about the Pkg-libburnia-devel mailing list