Musings on PHP

Max Bowsher maxb@ukf.net
Wed Sep 21 13:23:00 GMT 2005


Robert Richter wrote:
>> I didn't really intend to package PHP, but having got this far, I sort of
>> feel I ought to.
>> Which brings me to two major issues concerning any potential Cygwin PHP
>> package:
>>
>> 1) Two apache versions.
>>
>> I've no interest in Apache 1.3.x. Can I just package PHP for 2.x, and 
>> worry
>> about 1.3.x only if a potential maintainer steps forward?
>>
>
> I already got a PHP 4.3.10 version running on Apache 1.3.x and plan
> to add PHP to the Apache 1.3.x release. I am not sure if this is the best
> solution but maintenance effort decreases.

In the same package?
That doesn't seem like a good idea.
That is likely to confuse users, and will lead to unnecessarily large 
updates when one of Apache/PHP needs to be updated, but the other does not.

> On the other side a
> separate package could be included also by Apache2 and package
> conficts would be avoided.

I don't understand how this will avoid conflicts?
Although I have never explicitly tried, at the moment, it should be possible 
to install and run both apache1 and apache2 simultaneously.
If there are to be two independent PHP packages, we need to avoid file name 
conflicts between them, just like no files in the apache & apache2 packages 
share names.

Max.



More information about the Cygwin-apps mailing list