| Summary: | libmng-1.0.9 is released | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Håvard Wall <haavardw> |
| Component: | New packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | halcy0n |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
libmng-1.0.9.ebuild
libmng-1.0.9.ebuild libmng-1.0.9.ebuild |
||
|
Description
Håvard Wall
2006-04-03 09:05:37 UTC
Created attachment 83866 [details]
libmng-1.0.9.ebuild
Tested on x86.
If maintainer is needed, I could volunteer, (but I currently don't have status as a developer). I'm working as a software developer and bumped into the bugs in libmng-1.0.8 while testing it against Qt-4.1.3. I'll be doing these tests in the future as well.
Created attachment 84448 [details]
libmng-1.0.9.ebuild
Removed hard-coded dependency of lcms. lcms is optional and auto-detected by configure.
Removed wrong patching of Makefile.am which prevented autodetection of lcms.
We shouldn't rely on the automatic detection, but rather specify explicitly with $(use_with lcms) when we call econf. Otherwise the use flag is to just pull in the dep, which isn't exactly right :) Created attachment 84460 [details]
libmng-1.0.9.ebuild
Agreed. After testing further, neither jpeg nor zlib is hard requirements. Fixed in this third attempt.
Does the addition of these USE flags cause problems for any of the packages that DEP on libmng? Do those packages need certain use flags enabled to work properly? A list of them can be found: http://tinderbox.x86.dev.gentoo.org/misc/rindex/media-libs/libmng (In reply to comment #5) > Does the addition of these USE flags cause problems for any of the packages > that DEP on libmng? That would imply a bug in their dependencies wouldn't it? Or would it imply the lack of spesifying a use-flag dependency in portage? Anyway, I don't think it will cause many problems. This is what I've found: These packages have missing or incorrect dependencies: app-cdr/graveman: should depend on >=sys-libs/zlib-1.1.4, =media-libs/libmng-1.0.0. I really couldn't find out how these packages actually depend on libmng. They don't even have it listed in the ebuilds: app-editors/nvu These had optional support for libmng documented in the source code (probably autodetected?), but noe use flags in the ebuild: mail-client/mozilla-thunderbird www-client/mozilla-firefox www-client/mozilla www-client/seamonkey These have hard dependencies in the ebuilds, but no references to mng in the source code or documentation: app-emulation/pearpc x11-misc/vym These packages depends on libmng, but I couldn't find any references to the jng or zip functionality in the source code. app-office/magicpoint dev-embedded/pikdev media-gfx/bootsplash x11-libs/qt x11-libs/qt-embedded These packages had optional mng support, and should therefore be unaffected: dev-games/crystalspace I was unable to download and check the source code of this package, but it already depends on zip, and I would be very surprised if it depends on the jng functionality: x11-misc/kflog Bumped the ebuild Cool. Thanks alot! |
