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

[John Morrissey]

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. :-)

I have a few PHP-related packaging questions that I'll ask here. I also have
a couple (minor) non-PHP-related packaging questions; should I ask them here
too, or would d-mentors@ be better?

- 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?

A few questions on the draft PHP policy at
http://webapps-common.alioth.debian.org/draft-php/html/ch-php-libs.html :

- Has there been a consensus on package naming? It looks like existing PEAR
  modules are named php-$PEAR_PACKAGE_NAME, so I went with that and used
  php-crypt-blowfish.

- 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?

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