Re: PHPPEARpackages
> It's certainly possible to create a tool that would help package php
> PEAR/PECL modules.
>
> This issue has been discussed before:
> http://lists.debian.org/debian-devel/2004/02/msg01713.html
> http://lists.debian.org/debian-devel/2004/04/msg07277.html
These discussions focused on naming packages. I am interested in knowing
how to create the packages.
> However, I don't think that we should support PECL/PEAR as a replacement
> for dpkg, but handle it similarly to CPAN (dh-make-perl).
>
> I'll get started on a dh-make-php
As far as I can tell, the ideal dh-make-php would:
- Properly install all files, bsaed on package.xml locations
- Extract the summary from package.xml
- Extract the description from package.xml
- Extract the changelog from package.xml
- Extract the license from package.xml
- Possibly do something standard with tests, examples, and docs directories.
- Create all documentation using phpDocumenter
It seems that make-pear-pkg does some (or all?) of this. Is that the way
to go, or should I wait for dh-make-php?
Charles
--
Free offer! Free offer!
Rip a fender
Off your car
Mail it in for
A half-pound jar
Burma-Shave
http://burma-shave.org/jingles/1933/free_offer_free
Reply to: