[Php-java-bridge-users] obsolete files ? / zend extension ?

[<php...@li...>]

Hello, Jost
Today I updated the ./debian directory with some improvements and
prunings.
Still needs further tests to announce it, but should compile and package
from a plain cvs checkout, as per README.debian .

Maybe the files you cited were removed from the packages by now.
Could you try to compile yourself in a Debian or maybe Ubuntu (virtual)
machine?

The Debian php extension directory is calculated dinamicaly at
compilation time by the line (today) 37:

	PHP_EXT_DIR := $(shell /usr/bin/php-config --extension-dir)

To edit the java.ini dinamicaly, some shell tricks should be performed,
and the postinst and postrm scripts could become really tricky.
Previous versions of Debian php had such nasty tricks to edit and
"unedit" ini files.
Today, the php packages are much more cleaner [0], [1].

As the php extension dir location is calculated at Debian package
compilation time, it will shurely compile for future versions.

Maybe I missed something, but in this scenario are there still
significant benefits of using zend_extension enough to justify dirty
tricks at packaging? 
I am trying to clean the packaging files and rules as I learn more [2].
The target is lintian zero errors and warnings [4] against Debian Policy
[3].

Best regards.
Andre Felipe Machado
http://www.techforce.com.br

[0] http://bugs.debian.org/388697
[1] http://bugs.debian.org/388698
[2] http://wiki.debian.org/PkgSplit
[3] http://www.debian.org/doc/debian-policy
[4] http://wiki.debian.org/WhyDebianForDevelopers