Bug 341585

Summary:	media-gfx/digikam needs media-gfx/exiv2 compiled with xmp support in order to work with xmp tags.
Product:	Gentoo Linux	Reporter:	Fest <fest.in>
Component:	Current packages	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED INVALID
Severity:	enhancement
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Fest 2010-10-18 07:37:45 UTC

Digikam have kde-base/libkexiv2 in dependencies, which depends on media-gfx/exiv2. 
By default it compiled without xmp support, which leads to non-working xmp tag editor in Digikam. (issue in KDE bugzilla - https://bugs.kde.org/show_bug.cgi?id=247590)

So i'm asking about adding media-gfx/exiv2 +xmp to Digikam dependencies.

Reproducible: Always

Steps to Reproduce:
1. merge media-gfx/digikam.

Actual Results:  
portage install media-gfx/exiv2 without xmp flag.

Expected Results:  
portage install media-gfx/exiv2 with xmp flag.

Comment 1 Samuli Suominen (RETIRED) gentoo-dev

2010-10-18 09:01:48 UTC

I don't get your point.    Digikam is already fixed to report "Exiv2 supports XMP metadata: No" instead of "Yes" by upstream per the bug report you linked.
So why should another ebuild be forcing USE flags from another one if it's not really required?
As an example. It's not like every GTK+ based image viewer is forcing +jpeg from x11-libs/gtk+ in order to show .jpg images either

Comment 2 Fest 2010-10-18 17:47:12 UTC

Thanks for example. I thought about this, not like "additional filetype support" by as "non working feature". 

But since xmp the only metadata format that supports unicode - imho it should be default flag for media-gfx/exiv2 in desktop profile? Like "unicode" or "nls" use flags?