[pkg-php-pear] Crypt_Blowfish conflict between PEAR and phpseclib
math.parent at gmail.com
Mon Jul 1 08:54:44 UTC 2013
2013/6/30 David Prévot <taffit at debian.org>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> Le 30/06/2013 11:00, Mathieu Parent a écrit :
>> 2013/6/29 David Prévot <david at tilapin.org>:
>> I packaged php-crypt-blowfish because it was a Horde dependency at
>> that time. […] As php-crypt-blowfish doesn't have any
>> rdepends, it may be removed.
> Well, owncloud is currently its only rdepends then, thanks.
>> Also, is there any link between PEAR's Crypt_Blowfish and Owncloud
> They ship en embedded copy of it, yes:
> (And the owncloud Debian package instead depend on php-crypt-blowfish).
>> is this a fork, with compatible API? A quick read suggests that
>> it is compatible
> Thanks, I must have a closer look, and may eventually take over
> php-crypt-blowfish and use the phpseclib as a source instead of PEAR
> (can do a provide and conflict from php-seclib as a start).
>> Also, for the binary package name, ask pkg-php-tools. This will probably be:
> Wouldn’t that contradict the naming scheme? I thought that a package
> providing /usr/share/php/Crypt/Blowfish.php, taking its source from the
> Crypt_Blowfish PEAR package, should have been named php-crypt-blowfish.
This is not how pkg-php-tools construct the name.
> Is that reserved to source coming from pear.php.net?
You can play with /usr/share/pkg-php-tools/scripts/phppkginfo
debian_name <channel url> <pear name>
to see how it behaves.
>> Which is not very good (read dh_pear manpage about overrides).
> Did you meant dh-make-pear(1)?
I mean dh_phppear. dh-make-pear is outdated.
More information about the pkg-php-pear