Hi Simon,<br><br><div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> ===================================================================
<br>> --- desktop/trunk/libxfce4mcs/debian/changelog 2006-02-02 16:43:49 UTC (rev 471)<br>> +++ desktop/trunk/libxfce4mcs/debian/changelog 2006-02-05 16:38:45 UTC (rev 472)<br>> @@ -1,3 +1,11 @@<br>
> +libxfce4mcs (4.2.3-2) UNRELEASED; urgency=low<br>> +<br>> + * Make .so library version matching more generic to catch soname bumps<br>> + and to be consistent with libxfce4util and libxfcegui4<br>> + * Add myself to uploaders field
<br>> +<br>> + -- Jani Monoses <<a href="mailto:jani@ubuntu.com">jani@ubuntu.com</a>> Sun, 5 Feb 2006 16:56:43 +0200<br><br>Sorry, I meant to reply to this ages ago.<br><br>I don't think this should be committed. I thought if you were going to
<br>make 4.3 changes you were going to do them separately.</blockquote><div><br>I have specifically put this in trunk as it is good for both 4.2 , 4.4 and whatever else will come.<br>The comment even says it is done like the other libs.
<br>So these are not 4.3 specific changes. <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Also, I'm not happy with these changes. I'd want the package to not
<br>build (or at least not usefully ship a library) if the soname changed<br>and noone noticed. I don't think the packaging should ever encompass<br>more than one version of the library as there may be specific things</blockquote>
<div><br>It installs all .so.X.Y libraries from the package currently being built. If that contains<br>more than one soname version for the same library we're in bigger trouble anyway.<br></div>So with the same debian rule we are able to build all upcoming versions of xfce libs.
<br>and not just the one which has soname 2.0.0 for instance.<br></div><br>Jani