Since 0.8 version, UFRaw can read exif tags from more raw formats thanks to exiv2. It can be very useful if you have a canon DSLR and want to use clens on your output image.
Created attachment 89536 [details] ufraw-0.8.1-r1.ebuild I've added "exiv2" useflag.
This has nothing in common with gentoo bugzilla, please read the product descriptions when filing bugs.
Rather than adding an exiv2 USE flag, I would think that adding exiv2 as a dependancy with the existing exif USE flag would make sense - exiv2 adds support for exif information stored in Canon Raw files (.CRW), while libexif is for supporting Kodak .RAF files (at least according to the ufraw ChangeLog). As such, I have a ufraw-0.8.1-r1.ebuild in my local overlay with the following differnces from the main portage tree : 20c20 < exif? ( >=media-libs/libexif-0.6.13 ) --- > exif? ( >=media-libs/libexif-0.6.13 media-gfx/exiv2 ) 35c35 < `use_with exif libexif` || die "configure failed" --- > `use_with exif libexif` `use_with exif exiv2` || die "configure failed"
From what I understood, you have to choose between exiv2 and libexif when configuring ufraw. It is however unclear about which exif tag each library can read (I expect that each of those libs can read more than one type of raw file). In any case, your solution won't make it in the official ebuild as we don't want to depend on *two* exif libs that are likely to have overlapping features.
(In reply to comment #4) > From what I understood, you have to choose between exiv2 and libexif when > configuring ufraw. That doesn't appear to be the case - neither my own experience (ufraw compiled with support for both) nor a brief appraisal of the source would appear to require a choice. > In any case, your solution won't make it in the official ebuild as we don't > want to depend on *two* exif libs that are likely to have overlapping > features. Huh? To be able to handle the exif data in .CRW files, exiv2 is required. To be able to handle the exif data in .RAF files, libexif is required. Both coexist with no problems. However you do it, would you please add exiv2 as a dependancy. ufraw is less useful without it.
After thinking about it, the best solution seems to be two separate USE flags, as people without Canon cameras (like me :)) won't care about exiv2 and this would be an unnecessary dependency. And that works in the other direction with libexif. So I just commited 0.8.1-r2 with those two USE flags.
Just letting everyone subscribed to that bug know that for ufraw-0.9 that has just been released, exiv2 now does the main part of the exif work. Seeing one wouldn't want exif support without exiv2, I merged the two USE flags, as proposed initially by Jonathan Adamczewski.
