[Kde-imaging] Re: [Digikam-devel] Re: Git migration for 2.0.0 + code components re-structuring...

[Angelo Naselli]

In data giovedì 9 dicembre 2010 18:18:19, Gilles Caulier ha scritto:
> The goal is to host the current unstable code from trunk in digiKam
> package and use it with the digiKam and co release. This copy of
> unstable code will have API/ABI id increased to be installed in both
> to the system without to break anything.
You need to take care also that the version you release out of trunk
*have* to be upgraded by the next trunk (e.g. kdegraphics stable) version
to avoid conflicts.
Remember that a system that installs libfoo from a standalone package
can have conflicts when updates libfoo using another package.
I mean libkipi-kdegraphics and libkipi-standalone are in conflicts if
they produce same files in same position...
And certainly packager have to take in account the developer
version of that library...

Cheers,
-- 
	Angelo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-imaging/attachments/20101211/3ebedacc/attachment.sig