First of all, are all of the below listed packages are required for a specific service I am trying to run.

I am not extremely familiar with linux, but I do have my own server, root access etc, and have installed packages before.

My main concern is: does the directory I install the package place the other executables in the correct dirs? for example, if I install PHP in /mycreateddir/ will it function the same as if I installed it in: usr/lib? .. I am asking becuase in Windows, if you install an application from any directory, the default directory which all applications with be installed no matter where you initiate the install is c:/program files/ and all files, updates, etc are done in the required locations..

Does Linux RedHat Enterprize 4 follow a similar pattern?

And does it matter where I install the following packages?

1.) PEAR
2.) cURL for PHP 4.3+ and higher SSL support
3.) PHP Open SSL extension for PHP 4.3.0+ and higher
4.) PHP Perl Compatible Regular Expressions extension for PHP 4.3.0+ and higher

Thanks for any recommendations, assistance, tips etc! SOS

Assuming you have RPM packages for these, the rpm installer will put the files into the correct place when you run them. It does not matter which directory you install the RPM from. If you are compiling from source, you generally specify the destination directory by using the --prefix argument to configure.

btmiller,

thanks for the information. that does help.

i assume when you said: "If you are compiling from source, you generally specify the destination directory by using the --prefix argument to configure"

you are refering to the binaries?

Do you have a sample binary install command line example with --prefix used?

What directory do you normally store binaries or RPMs priopr to installing? Do you just create a temp dir?

I know this is a personal-preference question, but Im trying to base my decision off of some standard, if there is one.

Thank you

Source and binaries are just the opposite of one another. Source is where you have to go through ./configure, make, and make install to get it to function. That type of install is what btmiller was referring to when he spoke of using the --prefix arguement.

Just like windows, you can put compiled software anywhere you want, and then play with permissions of the location to allow everything to see and use some "created" location. To make things easier, and get things where they "should" be, most people place self compiled software in /usr/local/.

Binaries come from installing via .rpm files, using yum or any of the tools built around .rpm. Those have instructions built in on where they should be located, so you can install the rpm file from any directory, and it puts all the files where the "should" go, locations like /usr/bin/, /lib,. etc. The binary files require much less thought and planning, they are more of a "just work for me" solution.

Peace,
JimBass