Debian patches review

Hi,

As I do for my other package, here is a list with descriptions of the
patches applied (or to be applied) in the current Debian package. I don't
attach all of them to avoid flooding the list, but please don't hesitate
to ask :

lib_amaya.diff : Debian specific. Install to amaya instead of
Amaya-@APP_VER@ to make the package management easier. I have some plan to
make it more generic, so it could be integrated.

missing_class_ftbfs.diff : Fixes a build failure. Already merged into CVS

ptr_to_int_casts.diff : Fixes a build failure. Already merged into CVS

redland.diff : Fixes the use of redland library. Already merged into CVS

cascade_hbt.diff : Pass the host, build and target value when calling the
configure script for Mesa, wxWidgets, libWWW, redland. As it fixes
potential build/run failure when cross-compiling, I suggest it is applied.
(attached)

add_destdir_to_Makefile.diff :  Already merged into CVS

enable-system-wx.diff : Adds --enable-system-wx option to link against the
system provided wxWidgets library rather than building it and linking
statically. It might need a bit of polishing, but I guess it would be nice
to have this option available for everyone. (attached)

use_debian_fonts.diff : Debian-specific. Modifies fonts.gl.deb to use
Debian-provided Freefonts. (attached)

link_with_libtool.diff : Using the Debian-provided libtool for linking
removes some useless indirect linking, which is specially interesting when
it comes to redland. Applying this patch would probably bring much
improvement on other platforms, though. (attached)

dont_build_cextract.diff : Debian specific. It appears that the license
for cextract doesn't meet the DFSG. Therefore I have to remove it and stop
building it.

no_svg_in_homepage.diff : The Gdk error many people have seems to be
triggered by the Amaya SVG logo on the start page. Although the problem
seems to actually come from Mesa and/or Xorg, this is a temporary
workaround to let Amaya at least start.

I also started working on a patch to use the system provided libwww, which
I will submit as soon as I get it working.

As a sidenote, there I have two license problems with the content of the
official tarball :
-the cextract tool is not DFSG-free, so I will have to remove it
-the esstix fonts do not comply either, as they require the agreement from
the author to be modified.

Removing cextract is not much of a problem for me; however, I would like
to know how the removal of esstif fonts would affect the software itself.

Thanks for your help.
Should you require any further information, please do not hesitate to
contact me.

Regards,
Regis
-- 
"While a monkey can be a manager, it takes a human to be an engineer" Erik
Zapletal