where is the location of installed programs? in windows there is progam files.. hmm

kublador · 03-13-2003, 07:40 PM

where are my programs installed?
im confused..
there are too many directories in linux...
for example.. i just installed mozilla-1.2.1
i dont know where exactly it is...
please help me
i need it to ./configure galeon properly...

galeon's install file says:

./configure --with-mozilla-includes=your_mozilla_dir/dist/include --with-mozilla-libs=your_mozilla_dir/dist/lib --with-mozilla-home=your_mozilla_dir/dist/bin

what should i put in each value? for example..
--with-mozilla-includes=?

where should i point the include, the libs, and the home?
thank you very much =)

Crashed_Again · 03-13-2003, 08:13 PM

If your not sure where mozilla is you can do:

whereis mozilla

rmartine · 03-13-2003, 08:35 PM

When you install stuff from source you should thoroughly look through the README and INSTALL files. They usually tell you where the make install script will place the binaries. On my Red Hat 8.0 box mozilla 1.2.1 was installed into /usr/local/mozilla

Also you can control where files are install by using ./configure --prefix=/where ever/

Have Fun

doublefailure · 03-13-2003, 08:46 PM

if u can, i'd highly recommend using rpm for mozilla/galeon

as for your question,
it depends how you installed mozilla
if u installed from source(tar.gz is not necessarily source)
u willl have /path/to/source/mozilla/dist/include
thing is it might vary from version to version

if u 've used rpm, it probably be /usr/lib/include/mozilla

i would recommend using rpm for both mozilla and galeon.
if u want to go with source still, let me know

mhearn · 03-14-2003, 05:30 AM

Apps on Linux use a "prefix", the default for source installs is /usr/local, and most RPM packages install to /usr, for reasons that you really don't want to know.

Configuring Galeon should automatically pick up these values if you installed Mozilla without any special tweaks.

kublador · 03-14-2003, 11:05 AM

when you say "you install from source" what does it really mean?
crashed_again... did what you said.. i learned again something lolz.. thank you man...

so you mean all progs installed are in /usr/local ?
hmmmmm im just wondering..
i saw another ./mozilla-1.x.x directory on some folders...
hmmmm what are those other directories for?

acid_kewpie · 03-14-2003, 11:33 AM

no not all of them. could be in /bin could be in /usr/bin, could be in /usr/local/bin, could be /usr/X11R6/bin etc... for the binary programs ad then their (if they have any) additional libraries in their equivalent locations.

slakmagik · 03-15-2003, 03:09 AM

Install from source is when you configure, make, and install the source code rather than plug in the rpm. Usually something like app.tar.gz that you tar -zxvf on rather than app.rpm that you rpm -i on, or whatever. (Though, as doublefailure said, tarballs can be binaries, just like .rpms can contain source.)

As far as the differences in directory structure, Windows NT has a C:\Program Files with most everything about an app dumped in a subdirectory of that. But it also has user-specific info buried in the depths of "Documents and Settings". And, then, there'll be registry keys and dll's and whatnot sprayed all over the system.

Linux does look like it's a hell of a lot more complicated, but it just separates most things. Man pages to an app are in a subdirectory of man pages (instead of a help file in the same directory as the app) and libraries are in lib and executables are in bin and configuration is in home if user specific or etc if system-wide. It actually makes more sense after you get used to it and fits with Linux's kind of atomic structure - collections of tools instead of monster apps; bunch of configuration files instead monster registry; bunch of compartmentalized and relevant subdirectories instead of "Windows" and "Program Files". And it makes damage to a system, or changes to a system, much more localized and makes backup or protection of certain elements easier and so on.

Simplest way to get a grasp of it is just to realize it cuts across a different angle. Instead of a bunch of Mozilla stuff in one or two places 'down', it's going to be a bunch of related Mozilla stuff in a few places 'across'. I'm making up stuff for simplicity but, say - bin/mozilla is the executables, man/mozilla is the help, etc/mozilla is system-wide config, home/.mozilla is the user-specific config, lib/mozilla is the libraries, and so on. So instead of being so app-specific, you get task specific. I need help on Mozilla - man mozilla; I need to configure Mozilla - /home/name/.mozilla; I need to run Mozilla - bin mozilla. (Mozilla should be on your path and you just type mozilla, but maybe you see what I mean.)

And going on what acid_kewpie was saying, the specifics of that have further meaning, I think. /bin is going to mostly be important cli stuff, /sbin is going to be vital system cli stuff, /usr/X11R6 is going to be gui stuff, /usr/local is going to be stuff you added apart from the default distro package and so on. So if you downloaded Mozilla and installed from source, the executable is likely to be in /usr/local/bin. If that's so and something's looking for Mozilla libs, they're likely in /usr/local/lib.

Where's that Ramble Switch? *clicks Off*