Bugzilla Bug 91644

app-office/magicpoint links against libmng if it is installed, however it
isn't a listed dep and it doesn't honour the global USE flag either.  The
attached patch magicpoint-1.11b-mng_optional.patch changes the behaviour of
configure to only test, and therefore link, against libmng if --enable-mng
is provided on the command line.  The second attachment,
magicpoint-1.11b-mng_optional_ebuild.patch, updates the ebuild to make
MNG support optional dependent on the global mng USE flag.

  The second patch moves the bug #85720 fix in to src_unpack aswell, purely
because the optional MNG support requires the execution of autoconf to
update configure.in anyway so one might as well operate on only the
configure.in file for #85720 fix.

  In the course of looking at this bug I also had to endure the ugliness of
the head call warnings, so there is a third attachment to use the
fixheadtails eclass to fix this.  Once again it is only called prior to
autoconf's execution instead of changing generated files too.  Obviously
with current coreutils it is only cosmetic.

  One other minor issue appeared to me while looking at the magicpoint
ebuild, and that is the content of
${FILESDIR}/magicpoint-1.10a-r1-gentoo.diff.  Shouldn't the canonical
location of truetype fonts now be /usr/share/fonts and not a location in
/usr/X11R6?

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Created an attachment (id=58172) [edit]
magicpoint-1.11b-mng_optional.patch

Created an attachment (id=58173) [edit]
magicpoint-1.11b-mng_optional_ebuild.patch

ebuild changes necessary to support the optional MNG linking

Created an attachment (id=58174) [edit]
magicpoint-1.11b-fix_head_call.patch

Thanks for the patches. I committed them to CVS.
As for magicpoint-1.10a-r1-gentoo.diff, magicpoint w/ freetype
only searchs the directory (not looking into its subdirectories),
so there's no point changing it to /usr/share/fonts. Anyways,
magicpoint ebuilds do not enable freetype support atm
(they used to, though), so it doesn't do anything in reality.

  Thanks for info, it has cleared up my confusion about the fonts directory.  I
wasn't really all that sure what it was supposed to be doing that is why I
raised the issue as a sidenote, it just looked wrong ;)