Atomicorp

Cool thing that art now has PHP 5.x but what about the people that want to use PHP 4.x? Is it going to be supported? Could there be a different channel where we can get updates for that?

Thanks

The src.rpm for 4.4.2 is here: http://3es.atomicrocketturtle.com/packages/php/

I don't currently have any plans to maintain the 4.4.x tree at this time, unless there is a whole lot of community or commercial interest. I actually put together the first 5.0 rpm over 2 years ago, and staring at it in the archive every day.. I got the feeling that it was starting to mock me.

For what it's worth, we plan to stick with the 4.4.x tree for the next 8-12 months. I can forsee us sticking with php4 until php6 is ready, even if that means waiting longer than 12 months. For our customers, the benefits of 5 do not outweigh the fact that some customers' apps will break.

We want to use php4.4.2 on our production machines, and in all my preliminary testing on our staging server, I was able to use yum update, using your repositories I *thought*, to update to the 4.4.2 branch. Now when I follow the exact same process, yum update wants to install the 5.0 branch. We absolutely cannot use the 5.x branch at this time due to some of our customers having apps dependent on php4.

Am I doing something wrong/different perhaps, or did you change the repositories? How should I manually install from these src rpms? Any pointers? Will the src rpms install the necessary dependencies such as php mysql libraries, etc? Is there another way using yum that I can install the 4.4.x branch?

Ugh, thought I was going to have the first of our new production machines ready today. This has thrown me off, and any advice is appreciated.

For what it's worth, I'm certain I'm not the only one interested in keeping the 4.4x branch alive

http://www.php-mag.net/magphpde/magphpd ... eid,5.html

http://www.nexen.net/images/stories/php ... ieu.en.png

Use a dedicated system for building, or a build system like mock, or dar. Personally I use dar, since I do multi-distro builds. Mock is good for smaller one-off type building, it comes with FC4 and FC5.

Stupid question. When you say use a dedicated system, are you referring to not building on a *live* production machine (which seems obvious) or are you saying do not have any of the build tools on a production machine period (eg all the -devel packages).

I built the rpms from source on what will be a production machine. Would it be in my best interest to rebuild this box again using the rpms I built from source, or is it not a problem that I performed the actual build on the box since it wasn't in production at the time of building?

I just want to make sure I'm not missing your point. Thanks!

For example, each system I build for is nothing more than a chroot jail, they arent live systems in any way (cant boot them, etc). I then install every package available for that particular distro in the chroot. Thats not to say you cant build on a production box, I just dont recommend it, since you tend to have to do things like updating core packages (curl for example... can be a big php/apache killer) to build newer versions that will break backwards compatibility. If you dont mind getting stuck in that kind of environment (more commonly known as "freebsd" heh) then go for it.

Understood, I appreciate the clarification.

We too will probably stick with the php 4.4 / mysql 4.1 tree for a while as we have apps that depend on it.

I love the ART archive, but big moves like this cause us some problems. Have you ever considered providing commercial archives that don't change in version numbers? I'm sure for a small yearly subscription you'd get plenty of takers.

Yep, thats what I do with the ASL channel

rpm -U php-5.1.4-1.art.src.rpm
warning: php-5.1.4-1.art.src.rpm: V3 DSA signature: NOKEY, key ID 5ebd2744
error: cannot create %sourcedir /usr/src/redhat/SOURCES

nokey ?

error: cannot create %sourcedir /usr/src/redhat/SOURCES <- that directory doesnt exist