<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Il 21/01/2011 09:13, Michal Zajac ha scritto:
<blockquote
cite="mid:AANLkTimjQk5F+cG9Jdwy9c43M1pMV9kd+XjW92+CUdew@mail.gmail.com"
type="cite">
<p>1. Why do we have them? I think it is because they maintain
correct versioning of newer versions of shared libraries which
are used by binaries that use them on run-time<br>
2. Why it's worth to update them? Normally when library removes
something which makes packages depending on the older version
break upstream should bump the SOVERSION and we would bump the
name of the package. The symbols files are maintaining correct
versioning of shared libraries which are used by binaries on
run-time (so if they add something new, there are usually no
problems with the old packages). I think if for some wierd
reason upstream doesn't bump the soversion we would know it's
binary backwards incompatible already at the packaging stage<br>
3. How to update? From my experience each time there were any
changes to the symbols files I got a diff spewd out by
dpkg-gensymbols which had to be applied to appropriate *.symbols
file in packaging directory (debian/)</p>
<div class="gmail_quote">20-01-2011 20:47 użytkownik "Alessandro
Ghersi" <<a moz-do-not-send="true"
href="mailto:alessandro-ghersi@kubuntu.org">alessandro-ghersi@kubuntu.org</a>>
napisał:<br type="attribution">
</div>
</blockquote>
<br>
Ok thanks, +1<br>
;)<br>
<br>
</body>
</html>