digikam 2.0.0 packaging for distributions

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

digikam 2.0.0 packaging for distributions

Mark Purcell
Hi,

I'm the digikam packager for Debian GNU/Linux.

I have noticed that the 2.0.0 .tar.bz2 archive from sf.net is now
including a lot of extras that were distributed separately:

docs/{kipi-plugins,digikam}  will these continue to ship with the apps?

extras/kipi-plugins     was previous a separate tar archive
extras/libkdcraw        is also distributed with kdegraphics
extras/libkexiv2        is also distributed with kdegraphics
extras/libkface is unique to digikam archive
extras/libkipi is also distributed with kdegraphics
extras/libkmap is unique to digikam archive
extras/libksane is also distributed with kdegraphics
extras/libmediawiki     is unique to digikam archive

I can work around, but need to know if this is the plan for 2.0.0 final?

However, having the same libs released in the digikam archive and the
KDE SC kdegraphics archive is problematic for distributions.  Especially
as some are at the same soname libkipi.so.8, whilst others have
different interfaces KDE SC 4.6 kdegraphics ships libkexiv2.so.9, whilst
digikam 2.0.0 is shipping libkexiv2.so.10.

Mark
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: digikam 2.0.0 packaging for distributions

Gilles Caulier-4
I talk about this problem with Nicolas Lécureuil, the Mandriva packager.

The goal is to try to detect KDE 4.7.0 shared libraries about libksane, libkdcraw, libkipi, and libkexiv2. If there are present, through kdegrphics/libs, let's go to use it. Note digiKam must compile fine with KDE 4.6.x libs, but KDE 4.7 is better...

libksane is optional.

For libkface and libkmap, there still into kdereview. So there are not yet published with KDE. I already ask to KDE team for a migration to extragear/libs, but it's not yet done. Both are mandatory to build digiKam.

For libmediawiki, there is already in extragear/libs, but it's optional.

I hope this will clarify the situation. Nicolas, mutch patch digiKam SC CMakeLists.txt to handle external libs from KDE, if right version are available.

Best

Gilles Caulier

2011/7/2 Mark Purcell <[hidden email]>
Hi,

I'm the digikam packager for Debian GNU/Linux.

I have noticed that the 2.0.0 .tar.bz2 archive from sf.net is now
including a lot of extras that were distributed separately:

docs/{kipi-plugins,digikam}  will these continue to ship with the apps?

extras/kipi-plugins     was previous a separate tar archive
extras/libkdcraw        is also distributed with kdegraphics
extras/libkexiv2        is also distributed with kdegraphics
extras/libkface         is unique to digikam archive
extras/libkipi          is also distributed with kdegraphics
extras/libkmap          is unique to digikam archive
extras/libksane         is also distributed with kdegraphics
extras/libmediawiki     is unique to digikam archive

I can work around, but need to know if this is the plan for 2.0.0 final?

However, having the same libs released in the digikam archive and the
KDE SC kdegraphics archive is problematic for distributions.  Especially
as some are at the same soname libkipi.so.8, whilst others have
different interfaces KDE SC 4.6 kdegraphics ships libkexiv2.so.9, whilst
digikam 2.0.0 is shipping libkexiv2.so.10.

Mark
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel


_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel