<br><br><div><span class="gmail_quote">2007/5/8, Angelo Naselli <<a href="mailto:anaselli@linux.it">anaselli@linux.it</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Alle marted́ 8 maggio 2007, Gilles Caulier ha scritto:<br>> 2007/5/8, Angelo Naselli <<a href="mailto:anaselli@linux.it">anaselli@linux.it</a>>:<br>> ><br>> > Alle marted́ 8 maggio 2007, Achim Bohnet ha scritto:
<br>> > > On Sunday, 6. May 2007, Angelo Naselli wrote:<br>> > > > SVN commit 661885 by anaselli:<br>> > > ><br>> > > > Release 0.1.4<br>> > > > - fix libtools version-info
<br>> > ><br>> > > Hi, Angelo,<br>> > ><br>> > > looks like it get fixed in the wrong way ;)<br>> > ><br>> > > When I build 0.1.4 pkgs and install them, digikam io slaves only give
<br>> > errors like<br>> > ><br>> > > digikam: ERROR: : couldn't create slave : Unable to create io-slave:<br>> > > klauncher said: Error loading 'kio_digikamthumbnail'.<br>> > >
<br>> > > Reinstalling 0.1.1 and digikam works again.<br>> > ><br>> > > Anyone else tried to run an app build with 0.1.1<br>> > > to run with 0.1.4?<br>> > hmmm are this comment the reason?
<br>> > (Depreciate: used internaly by digiKam core.)<br>> ><br>> > Gilles you changed a lot of methods from protected to private,<br>> > I guess if that was the cause...<br>> ><br>> > Let me know we can release a new version promptly.
<br>><br>><br>> sure<br>hmm Gilles can we add a new policy for that? I mean if we decide<br>that some methods become deprecated, we should release a version in which<br>they are in yet, but interface and documentation say they are deprecated.
</blockquote><div><br>The methods have always annoted depreciate since first release on libkexiv2. </div></div><br>Gilles<br>