[php-maint] Packaging questions re: ITP: php-crypt-blowfish (#597324)

John Morrissey jwm at horde.net
Fri Sep 24 17:18:14 UTC 2010


On Sat, Sep 25, 2010 at 12:55:47AM +0800, Thomas Goirand wrote:
> John Morrissey wrote:
> > I'm a non-DD and am working on packaging Crypt_Blowfish. It seems like a
> > good idea to coordinate with the Debian PHP maintainers. :-)
> 
> Yes it is. Thanks for doing so.
> 
> By seeing your email, I wonder: are you working on the horde project?

I used to be on the Horde core team, but I haven't been involved with the
project for a while. The domain name is coincidence; I registered horde.net
and they registered horde.org within a year of each other. :-)

> > - Some PEAR packages allow tests to be included in /usr/share/php/test{,s},
> >   but some packages (php-mail, for example) explicitly remove the tests.
> >   However, php-mail never moves the tests to /usr/share/doc/$package,
> >   as the rules comment says:
> > 
> >     # remove duplicated files, these files are in /usr/share/doc/package
> >     rm -rf debian/$(package)/usr/share/php/tests
> > 
> >   Should I just leave the tests for Crypt_Blowfish in /usr/share/php/test?
> 
> By Debian policy, the docs of all packages have to be in /usr/share/doc,
> and PEAR packages are no exception. However, it is a good idea to to add
> a symlink. Something like this:
> 
> 	ln -s ../../doc/$(package) \
> 		debian/$(package)/usr/share/php/tests/$(PEAR_PKG)

Is that the same for tests, though? In other words, are tests considered
documentation and should therefore be installed/symlinked into
/usr/share/doc/$package?

> I have in fact found that CDBS does that, my own PEAR packages aren't
> doing it yet, but I guess I will be able to add this later on.

Is there a common opinion about whether to use CDBS or debhelper for PEAR
packages? I see some PHP packages use CDBS, but many more use debhelper.

> > - Section 4.2.2 says maintainer scripts should register/unregister PEAR
> >   packages, but it looks like existing packages just allow the .reg to be
> >   included in the package. Is including the .reg Good Enough?
> 
> What we always do is using:
> 
> $(PEAR) install -f -n -R debian/$(package) $(pear_pkg)/package.xml;
> 
> to install the PEAR library, because the source package xml file is
> containing path where to install all .php source code. You should do
> like that too. Then yes, keeping the .reg is what should be done, as
> much as I understand, and you should remove other files in
> /usr/share/php/.registry once the package is installed.

Ok. I wasn't sure if including the .reg in the .deb was the "best" way, or
if the maintainer scripts should call pear(1) to register the package with
package.xml when the package is installed.

I'll leave the .reg in the package.

> While I think about it, I think it would be a good idea to put your
> packaging in git.debian.org (which is also Alioth).

I have an Alioth account (jwm-guest); should I be able to push my
repositories to git.debian.org/pkg-php without any extra permission?

> Once you are done, I'd be happy to have a quick review of your package.

Thank you.

I'd also like to package Net_DNS (php-net-dns, #597966) and adopt
Services_Weather (#529687). Packaging for PEAR modules seems
straightforward, so working on these too should be easy. Would you be
willing to give them a once over too, once finished?

john
-- 
John Morrissey          _o            /\         ----  __o
jwm at horde.net        _-< \_          /  \       ----  <  \,
www.horde.net/    __(_)/_(_)________/    \_______(_) /_(_)__



More information about the pkg-php-maint mailing list