DirectFB depends on giflib which is now blocked by libungif, which other packages require (and I would like to move to anyway). Suggest DirectFB ebuild is updated to support either GIF library. Reproducible: Always Steps to Reproduce:
Don't know really which package depends on libungif, if it's some other package then those covered in Bug 85720, then post to that bug. There is nothing wrong w/ dev-libs/DirectFB ebuild, marking this bug as invalid.
No, there is nothing wrong with DirectFB, but there is also nothing wrong with adding support for libungif to it by changing the dep from: gif? ( media-libs/giflib ) to: gif? ( || ( media-libs/giflib media-libs/libungif ) ) libungif is a superset of the giflib API, and doing this would allow someone to have only libungif installed on their system.
(In reply to comment #2) > No, there is nothing wrong with DirectFB, but there is also nothing wrong with > adding support for libungif to it by changing the dep from: > > gif? ( media-libs/giflib ) > > to: > > gif? ( || ( media-libs/giflib media-libs/libungif ) ) No. Won't happen, we will get rid of libungif completely as soon as possible. > libungif is a superset of the giflib API, and doing this would allow someone to > have only libungif installed on their system. No, libungif is a cripled version of giflib, created due to patenting issues that are now gone, and so will be libungif gone.
Apologies, I wasn't aware that the idea was to remove libungif from the tree, having not seen that giflib had merged with libungif.
(In reply to comment #4) > Apologies, I wasn't aware that the idea was to remove libungif from the tree, > having not seen that giflib had merged with libungif. I explicitely pointed you to the relevant bug on removing libungif in comment #1. ;) Closing.
