php-java-bridge for Debian
This Debian package was compiled for installing php5 C modules, j2ee server,
docs and development files using separated packages.
Also, it must use Sun Java 6 and Tomcat 5.5, as of today.
You do not need C implementation and php J2EE server versions simultaneously.
You must use the J2EE version as soon you could, as C implementation is obsolete
and unmaintained. This is the last release that it will be compiled and
It will still be built from sources, for those who want.
This version is not compatible with php 4.x.
Use the command
debuild -rfakeroot -uc -us
at a directory you downloaded the .dsc, .changes, .diff.gz, orig.tar.gz files
and given you already have all devscripts tool chain Debian packages installed.
Compilation against GCJ is possible, but some tweaks must be done. Read the
other document files.
This package uses an EXPERIMENTAL and TOO permissive Tomcat 5.5 security policy.
Only suitable for security benign development environments.
Java security is not actually enough for blocking malicious code from php.
The production quality solution should be using Security Enhanced Linux
Read more at the "devel" package,
This version includes minimal SE Linux rules for starting Tomcat 5.5 and
Please, contribute improved rules to the project.
1. Creating and Building Debian package directly from CVS
Most steps are only needed if you will commit a new version to the repository.
If you want only to build an already commited version, you will need only create
a local working area (checkout module) as anonymous cvs user and then jump to
the step "building the package".
1.1 Creating package
1.1.1 Create your local project area (checkout module to your local CVS area).
The commands below are suitable for cvs commiters. Use your sourceforge cvs
If you are only building the package, use anonymous cvs checkout as instructed
in the URL.
cvs -d:ext:firstname.lastname@example.org:/cvsroot/php-java-bridge checkout php-java-bridge
Now you should have your own local area (checked out module) in
If you are only building the package, jump to the step 2.
126.96.36.199 If you are trying to merge a downloaded and then expanded src.tgz into
the cvs tree, use the command below, adapting it to the suitable version.
cp --recursive --update --verbose --archive --preserve php-java-bridge-5.2.2/* --target-directory=php-java-bridge
1.1.2 Commit the (eventual) changes to the repository. Ideally, you will not to
do this, if step 188.8.131.52 is not needed.
1.1.3 Create an upstream tag. The formating is VERY strict. Adapt to the
cvs -f tag 'upstream_version_5_2_2' '.'
1.1.4 Create or edit the Debian php-java-bridge specific patches.
dpatch-edit-patch patch 10_MakefileFrag_patch
Copy around from a personal template or edit the Makefile.frag into the
Exit dpatch shell.
All your modifications were being recorded and will result in the defined patch
file name into the ./debian/patches directory.
1.1.5 Modify the Debian changelog in the correct way. It is very important to
follow the strict formating, as the Debian changelog is actualy used as one of
the package control files.
debchange -v 5.2.2-1
1.1.6 Modify some other */debian files, if needed.
1.1.7 Commit all changes.
1.1.8 Create the Debian version tag. The formating is very strict. Adapt to the
cvs -f tag 'debian_version_5_2_2-1' '.'
2. Building the package from cvs tree.
If you are only building the package, you could use the anonymous cvs pserver
login and checkout as explained in previous item.
Hint: You need to specify the absolute path to the temporary scratchpad working
area instead of ~/.
cvs-buildpackage -rfakeroot -uc -us -R. -W/home/andremachado/compilation_tmp
The generated files will result at the specified temporary scratchpad working
-- Andre Felipe Machado <email@example.com> Thu, 28 Jul 2009 10:35:10 -0300