Closed (won't fix)
Project:
Quickstart: Prebuilt Drupal Development Environment
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
14 Sep 2010 at 02:48 UTC
Updated:
8 Dec 2010 at 04:58 UTC
I have had a couple issues with modules not working with PHP 5.3, also I found that some distributions (openatrium, openscholar) require PHP 5.2. So I propose to use PHP 5.2 as a safer pick, both for D6 and D7.
Comments
Comment #1
rfayThis is a valid concern, although I'd rather see all modules get fixed.
On drupal.org we test using PHP 5.3, including core and D6 contrib. But it's true that in the real world, there are warnings emitted on some contrib modules. Of course I encourage anybody who sees these to file an issue (and a patch, if it's in their realm) when they see this. But that doesn't solve the problem for everybody.
So probably a general, practical dev environment should come with 5.2.
One of the various articles on how to do PHP 5.2 on Lucid is at http://randyfay.com/node/63.
Comment #2
MichaelCole commentedHi,
IMHO, moving forward, D7 and 5.3 are the future. I'd like to focus on PHP 5.3 as the default choice for development.
If someone could submit a shell script to downgrade Quickstart to PHP 5.2 (and revert back), I think it would make a great addition.
QS 0.6 originally had this, but it was a PITA to maintain. (Check the lamp install script - also be sure that both apt-get and aptitude won't overwrite - "pin" and "hold").
Useful options, sensible defaults,
Mike
Comment #3
jedihe commentedHi Michael,
I didn't know about the difficulty of maintaining the package with PHP 5.2; definitely that reason alone is important enough to stay with 5.3
Could you point me to the install script, so I can check if there's something I can do about it?
Comment #4
MichaelCole commentedHi Jedihe,
Best to look in ~/quickstart/quickstart-3-lamp.sh, back a few versions. I pegged and pinned PHP to 5.2, but once D6 was ready for 5.3, I removed it because it was fragile and didn't get security updates.
Thanks for helping out :-)
Mike
Comment #5
MichaelCole commentedPostponed waiting for patch.
Comment #6
MichaelCole commentedHi, I won't get around to this, but would accept a patch if it was submitted.