[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 251894] kdemultimedia should be able to use external
From:       Gökcen Eraslan  <gokcen () pardus ! org ! tr>
Date:       2010-10-12 6:50:34
Message-ID: 20101012065034.E294C72173 () immanuel ! kde ! org
[Download RAW message or body]

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





--- Comment #7 from Gökcen Eraslan <gokcen pardus org tr>  2010-10-12 08:50:33 ---
(In reply to comment #6)
> Gökcen, why the separate package dependency? The thumbnailer doesn't much more
> than calling into libffmpeg to get a video frame. And what it _does_ more isn't
> needed in the KDE thumbnailer (conversion to PNG or JPEG).

Some distros have a seperate ffmpegthumbnailer package:

http://svn.pardus.org.tr/pardus/2009/devel/multimedia/graphics/ffmpegthumbnailer/
http://svn.mandriva.com/svn/packages/cooker/ffmpegthumbnailer/
http://www.archlinux.org/packages/community/i686/ffmpegthumbnailer/
http://packages.ubuntu.com/lucid/libffmpegthumbnailer4

it's a project lives in http://code.google.com/p/ffmpegthumbnailer/

What I'm trying to say is, embedding external libraries in applications, is not
a good behaviour since it's both harder to maintain code duplicates from the
perspective of package maintainers (for example if there is a patch about
ffmpegthumbnailer, package maintainer will try to patch both ffmpegthumbnailer
package  and embedded ffmpegthumbnailers in other packages) and for security
reasons.

For example Debian has a list of embedded code copies:

http://svn.debian.org/wsvn/secure-testing/data/embedded-code-copies?op=file

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]