tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Prefixing PHP packages with ${PHP_PKG_PREFIX}



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.

Attachment: pgpx729zqPFUc.pgp
Description: PGP signature



Home | Main Index | Thread Index | Old Index