I made some enhancements to the imagemagick-5.5.7.15.ebuild first some USE-flags for (it's better this way!): - lzw (LZW compression) support - dps (Display Postscript) support - exif (EXIF tag parsing) support - jp2 (JPEG v2 / jasper) support furthermore support for 'static' USE-Flag: +static builds only .a files -static builds only .so files, adding -fPIC and --with-modules and then a little enhancement to the 'freetype' USE-Flag: - adding --with-windows-font-dir=/usr/X11R6/lib/X11/fonts/truetype/ finally, I removed the --with-fpx (FlashPIX) option, because we need an ebuild for libfpx first and then we should have an USE-flag (ie. 'fpx') for it. FlashPIX libfpx can be downloaded here: ftp://ftp.imagemagick.org/pub/ImageMagick/delegates/ please use my attached patch to apply the enhancements to media-gfx/imagemagick-5.5.7.15.ebuild it's time for imagemagick-5.5.7.15-r1 ;-) Reproducible: Always Steps to Reproduce:
Created attachment 29456 [details, diff] imagemagick-5.5.7.15.ebuild.patch patch for media-gfx/imagemagick/imagemagick-5.5.7.15.ebuild
btw: http://imagemagick.org/www/download.html 6.0.0 stable is out! I have to check, what's new and what 'configure' says. I suggest to first apply my patch to 5.5.7.15 and then we check the 6.0.0.
ok, I checked 6.0.0-2. first of all, perlpatch.diff is broken now. configure has only some minor addons. But I have some problems to compile. Seems to be some work... :-/ But meanwhile, I found, that there's imagemagick-5.5.7-17 ;-) I optimized my patch for imagemagick-5.5.7-15 and offer a complete ebuild for imagemagick-5.5.7-17. It will be attached in a few minutes...
Created attachment 29462 [details] imagemagick-5.5.7.17.ebuild new ebuild for imagemagick-5.5.7-17 includes all enhancements! removed 'dps' USE-flag, merged it with 'X' USE-flag builds and works perfectly on 3 of my PCs.
remind, remind, remind! ;-)
*** Bug 36349 has been marked as a duplicate of this bug. ***
what happend to these enhancements in 6.xx series?
Almost every enhancement had been added to portage. Closing this bug.