On Wed, 27 Nov 2002, Ged Haywood wrote: > Date: Wed, 27 Nov 2002 20:56:01 +0000 (GMT) > From: Ged Haywood <[EMAIL PROTECTED]> > To: Jan Theofel <[EMAIL PROTECTED]> > Cc: mod_perl mailinglist <[EMAIL PROTECTED]> > Subject: Re: segmentation fault using a startup file > > Hi Jan, > > On 27 Nov 2002, Jan Theofel wrote: > > > Am Mit, 2002-11-27 um 17.33 schrieb Ged Haywood: > > > > > > What is it about compiling your own Apache that troubles you? > > > > It is a lot of work to do. > > Only the first couple of times. Takes me about two minutes nowadays.
I agree. The first few times I compiles anything on Unix, I thought "Wow, this is hard." Now I understand how things fit together and why it's a Good Thing to compile your own stuff. I feel dirty now when I use RPMs of Perl, Apache, or vi. > > Especially because we use SuSE Linux Enterprise Server which is a > > hihgly integrated system and we would loose the benefits of this > > system when we compile apache on our own. > > I don't understand that at all. Can somebody help me out here? A few months ago I tried out some different Linux distros. I liked Debian a lot until I got this wierd feeling about system dependencies on their own Perl. I ditched it within hours of that as I felt that it might prove easy to break the system. If you feel that you can't compile your own Apache on SuSE, you should probably consider a different distro for your web server and rely on those other nice bits on systems where you can do without the flexibility of compiling your own stuff. What will you do when the next security hole is found in Apache and you can't upgrade for fear of breaking your system? ky
