Which namespace to use for PECL packages in the PHP organization?

[cmb69]

This issue came up recently in php/pecl-file_formats-yaml#88 (review). Since it likely affects a lot of packages, I think it's worthwhile to track it here.

[asgrim]

Yeah no decision as such has been made, so maybe pecl is the best bet?

[asgrim]

Note, affects so far:

• Added a composer.json to enable support for PIE pecl-file_formats-yaml#88
• Added a composer.json to enable support for PIE pecl-datetime-timezonedb#12 (arguably, this one does really belong in php/ namespace, perhaps?)
• Added a composer.json to enable support for PIE pecl-encryption-mcrypt#20

[cmb69]

The timezonedb is already part of php-src; the PECL packages are just so users can update this, if they want to (works as drop-in replacement). So in my opinion, this can use the same namespace as other extensions.

[remicollet]

IMHO and from Packaging PoV, I think pecl is the best choice and that php should be avoid.

In RPM (from Packaging Guidelines) we use php-<vendor>-<project>

So using pecl as namespace will be perfect, as will result in the same name (ex: php-pecl-apcu)

Switching to php will be very confusing, package will have to be

• php-php-foo which looks terrible
• php-foo (duplicated word removed), but this will be confusing wth ext build from "php-src"

[asgrim]

Worth noting that this specifically pertains to the "vendor namespace" part of the "package name" for the purposes of submitting the extension onto the Packagist site, not the "extension name" (which will remain the same as when it is/was on pecl.php.net).

So, for discussion sake (I am not saying this is the final decision), lets say we used the package name of pecl/timezonedb in composer.json, the extension name is still timezonedb as it always has been historically:

[asgrim]

No further comments, so I'll update the three affected repos to use pecl/ namespace.

[remicollet]

Notice: use pecl as vendor name is not easy, see composer/packagist#1496