RE: [cobalt-users] How I got Apache 1.3.9 with PHP 3.0.14 on RaQ2 (and MySQL)

["Neil J. Kemp" <neil@xxxxxxxxxx>]

>FYI, I'm running PHP 3.0.7 from the Cobalt RPM (or package?) and MySQL
>3.22.27 from the source on the MySQL site.  I have the tar files for PHP
>30.14 and Apache 1.3.9.  I wouldn't mind upgrading to the latest stable
>version of MySQL.  Is it important to do that before upgrading Apache and
>PHP or can I do it later?

Well I'll be completely honest here. I don't know. Although if you compile
php --with-mysql and later when u upgrade mysql this stops working, you
SHOULD just have to recompile apache+php again.

>> *DISCLAIMER!* THIS WILL INVALIDATE YOUR WARRANTY!! DO SO AT YOUR OWN
RISK!
>
>I think I'm well past that point!  Er, I mean - I think we both know that
my
>original question and your subsequent answer were merely rhetorical in
>nature.  The RaQ2 more than meets any enduser's needs out of the box.

I know and it wasn't really aimed at you, but anyone else that wanted to
upgrade. It was more to cover my own back! ;-) Gotta love disclaimers! ;-)

>Is there a standard location for storing patchfiles on Linux?  I don't
>recall having ever run "patch".

No. You can store it anywhere you like. As soon as you've "patched" the
source code, you can delete the .patch file. The source code too can be
unpacked anywhere you want. I tend to do mine under /root somewhere, but
other people seem to use the location of /usr/src/redhat/SOURCES (proper
place?) either way once you have your binary and any relevant libraries
installed for whatever program you should be able to delete the source with
no consequences.

>> Watch for any error messages! All should go well! ;-) If it has gone pear
>> shaped at the worst you should just be able to swap the /usr/sbin/httpd
>> backup into place and restart httpd again.
>
>But now I'm stuck with a version of PHP I can't run, right?  I have a full
>backup of the directories that should be affected so I guess I can also
>reload from the backup (I hope).

No, because you are only swapping the httpd binary and modifying two lines
in the httpd.conf undoing these two stages will undo all the work. When you
did the make install under PHP it dumped stuff in the Apache 1.3.9 source
NOT over the existing Cobalt stuff. I don't know quite what would happen if
you did a make install for apache. Probably break a few things. I've never
really looked - never needed to ;-) All I've ever wanted is that new binary.

>Neil, not only does it help - it's put me in a very good mood!  I'm anxious
>to give it a shot and report a successful install back to the list.

Glad to help!

--Neil (Now with all new improved Geekcode!)
(Helps if you read the instructions properly!) ;-)

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12 - http://www.geekcode.com/
GCM/IT d s: a-- C++++$ UL++++$ P++> L+++$ E- W+++$
N- !o K- w++++(+)$ O M-- V- PS PE Y PGP++(+++) t+
5 X+ R- tv++ b+> DI++ D+++ G++ e h! r+ y+
------END GEEK CODE BLOCK------