[pkg-php-pear] Creating a PHP PECL team

[David Prévot]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi,

Le 10/10/2013 14:39, Lior Kaplan a écrit :
> On Thu, Oct 3, 2013 at 1:12 PM, Mathieu Parent <math.parent at gmail.com>wrote:
>> 2013/10/2 Lior Kaplan <kaplan at debian.org>:

>>> While we try to reduce the load of the PHP team, and move non core PHP
>>> packages to the PEAR team, I think we've mixed too much in one team.
>>>
>>> I would like to split the PHP extensions, mainly coming from PECL, to a
>>> separate team. The reason is to split arch:any packages which are effected
>>> by PHP transitions (e.g. the 5.4 support patches) to arch:all packages
>>> which just need PHP to work.

>> Good idea. But I hope it won't prevent people from going to this new
>> team because "compilation is hard" (making a PECL package is not
>> harder than a PEAR package).

I’m new into the PEAR team, so I may not see the big picture, but the
PEAR team doesn’t look much crowded. I came here because I’m mainly
interested to outsource embedded copies of code shipped in a package I’m
interested in (owncloud). Since I joined this team, I tried to help push
forward the “Build-Depends on pkg-php-tools” goal, and if the PECL team
had been separated from the PEAR one, I might have been spooked and not
looked into packages like php-ssh2 (maybe for the best ;).

That said, I wouldn’t be against a clear separation between the two
teams (I may simply not join the second one to focus into the PEAR one).

Regards

David


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBCAAGBQJSVxK0AAoJEAWMHPlE9r08cykH/R3uG1ucXk3C2ok2pDmUGVsG
ya8XFLV1/aNZBZMgVZr1ImJWqDvl4QlGYn5FhZSTMigwq1wJw+NZni2lprsaVbIR
IRjfERvoHfo59QfOksjDaA6rX4gU9MIvudULVA6d20S1JGjuKvC+eauWBrJRN7no
x8i6btFAcy/KMJjoGoLg0Kg9RZwwprMpVkfdPQ3XHHY29V0DMUs9esfQWLZfgOkq
7AaYKNasjA1YkyN+YE4ndosBdRZ71caE2XLJR+o3awK2g/kQqXyzqj45iGI0cxz8
ooge0U4+S13LshyA6pcslqFtgNyirR6gb31EMLiO+K1SrhGRVj0lJ2mFNOR3alY=
=o77q
-----END PGP SIGNATURE-----