I learned about the package dh-make-php, which would make the packaging of eZ
Components very easy, based on the pear packages provided by upstream.
Necessary steps:
mkdir ezc-packages
cd ezc-packages
pear channel-discover components.ez.no
pear download-all -c ezc
export DEBFULLNAME="Thomas Koch"
export DEBEMAIL="thomas.koch@ymc.ch"
#all normal packages get prefixed with php-ezcomponents
for C in $(ls -1| grep -v eZComponents); do \
dh-make-pear --prefix php-ezcomponents- $C;\
done
# The metapackage will become php-ezcomponents
dh-make-pear eZComponents-2008.2.1.tgz
# Put all the dependencies in the control files.
for C in $(find . -maxdepth 1 -type d); do \
../get_package_dependencies.php $C; \
done
# put in the bugnumber in the changelogs of all packages
# see e.g. vim help chapter 26.3
* Initial Release (Closes #478755).
# copy a copyright file in all packages.
#rm extra LICENSE, dummy files:
find . -name LICENSE -exec rm {} \;
find . -name dummy -exec rm {} \;
#build all packages
for C in $(find . -maxdepth 1 -type d -name "php-*"); do \
cd $C; dpkg-buildpackage -rfakeroot -kC5D1DD42; cd .. ;\
done
# check all packages
for C in $(ls -1 *.deb);do echo $C; lintian $C;done
----------------------------------
Remaining issue:
If upsteam would provide better descriptions in the pear messages, then
one would avoid editing them for the Debian packages. I filled an issue
about that, but it has already been closed as "won't do":
http://issues.ez.no/IssueView.php?Id=14503
The workflow can be repeated for every new release of the components.
The php script for the dependencies is attached.
Any objections against this workflow?
Best regards,
--
Thomas Koch, YMC AG, http://www.ymc.ch
Phone: +41 (0)71 / 508 24 86
Attachment:
get_package_dependencies.php
Description: application/php