[Digikam-devel] [Bug 252964] Please remove libs from kdegraphics and make independant

[Tomáš Chvátal]

https://bugs.kde.org/show_bug.cgi?id=252964


Tomáš Chvátal <scarabeus at gentoo.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |scarabeus at gentoo.org




--- Comment #8 from Tomáš Chvátal <scarabeus gentoo org>  2011-01-28 22:01:36 ---
(In reply to comment #7)
> I re-open this file due to change in digiKam 2.0.0 which is now a collection of
> code including kipi-plugins and all kdegraphics/libs (devel version, increased
> than kdegraphics/libs)
> 
> In fact kdegraphics/libs still avaialble, but digiKam will be published now
> with all kdegraphics/libs require to run digiKam and kipi-plugins.
> 
Hello Gilles,
I must strongly object to this idea.
You introduce possible security threat and possibility to introduce bugs just
thanks to the code duplication you are right now doing. For more i really
recommend fedora guys description and reasoning why the bundling is bad
<http://fedoraproject.org/wiki/Packaging:No_Bundled_Libraries>.

I know you probably think you are making things easier for us maintainers but
contrary you are just making sure that we wont probably ship the named versions
of digikam at all. Given the fact we will allow only official libraries to be
linked we wil have to wait onto the official libs to be released and then use
those if possible. Anything that uses bundled libraries at this scale wont be
able to get to Gentoo main tree at all (also i am quite sure at least debian
and redhat guys will do the same).

So how should one approach issues with libraries like this:
1) use only older code and rely on that - not quite bright
2) conditionaly enable more features when linking to some version - really
smart

So given we choose the second option we will be able to ship digikam with
"older" libraries where you can develop shiny new features (most applications
still support kde 4.4 and just few have beta releases that start to require
4.5). If we as packages find that libraries were updated (given soname change
or whatever else [user updated his kde]) it will trigger update of the digikam
itself, so it enables more features that will be availible at hand for the
user.

Tiny example of what i mean by second possible option (sorry for python, but i
aint exacly c expert but it is just proof of concept anyway)

import sys
if sys.hexversion < 0x02070000:
    # do complex calculation with some features
else:
    # user gave us shiny new python so we can use full features YAY

I really hope we will convince you guys to change your decision because i
really dont want to remove digikam from main tree since I am its user too. :)

With best
Gentoo KDE Team Lead
Gentoo QA Member

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.