Re: Prefixing PHP packages with ${PHP_PKG_PREFIX}

[matthew sporleder <msporleder%gmail.com@localhost>]

On Tue, Sep 8, 2015 at 8:43 AM, Greg Troxel <gdt%ir.bbn.com@localhost> wrote:
>
> David Sainty <david.sainty%gmail.com@localhost> writes:
>
>> On 02/09/15 03:44, Takahiro Kambe wrote:
>>> Hi,
>>>
>>> Thanks for your replies.
>>>
>>> And I'll change these packages by adding simply ${PHP_PKG_PREFIX} to
>>> PKGNAME.  (No PKGPATH change.)
>>>
>>> o PKGNAME prefix with ${PHP_PKG_PREFIX}
>>> o TBD
>>>
>>>      security/zoneminder
>>
>> I'm not sure if ZoneMinder is the odd package out, but it would be
>> wrong to prefix it with the PHP version.  The PHP dependency is
>> actually controlled by a package option, it's legal to build the
>> package without Apache/PHP bits explicitly enabled, and thus no PHP
>> dependency at all.
>
> This is exactly the sort of case I was talking about in foggy terms, but
> explained convincingly for a particular example.
>
>> If prefixing becomes a hard rule, I'd say ZoneMinder should be split
>> into component packages - the web front end one getting the
>> prefixication.
>
> I don't think having prefixes should be a rule, exactly because of cases
> like this.
>
> Regardless of the phpXY- issue, packages being split instead of options
> is a good thing, modulo the pain.   Split packages with just one
> language are then naturally prefixed.
>
> Arguably the bigger deal is making e.g. php55 and php56 be able to be
> installed at the same time.   Or perhaps it doesn't really matter which
> version is used, as long as its reasonably modern, and there's no need.


There are a lot of programs that are written in perl but do not need a prefix-
percona-toolkit is a great example.

ditto python-
hellanzb

Why should php be any different?  libs should be prefixed, programs should not.
A web-app (magento) is a little more tricky but (imho) *should* be
prefixed since
it is not unreasonable that i may need to run php55-magento AND php56-magento.