hi

i've noticed that even though i give --prefix=/usr/local
it only applies to binary files mostly
and many files are copied to
/usr/share instead of /usr/local/share
/usr/lib instead of /usr/local/lib

can i force it to use /usr/local directory instead?

so that i don't have to reinstall programs after upgrading to mand8.3 or so..

my assumption is if i keep /usr/local directory in seperate partition..
and install everything under it
i can safely use programs that i installed after system upgrade..
correct me if i'm wrong with this

thank you...

Do you really want to go here

I always install under /usr/lcoal/app_name or /opt/app_name which some would sa voliates Linux filesystem standard

./coonfigure --prefix=/usr/local/app_name

It depends when you want it to start, for instance
only the root filesytem is mounted in single usre mode,
but then you don't need or want apache to start in single
user mode.

i mean..
for the programs that i'm gonna install not by installation cd..

when i install programX
programX's files are distributed under
/usr/local/programX
/usr/share/apps/programX
/usr/lib/programX

is it a bad idea to force programX be installed?
/usr/local/programX
/usr/local/share/apps/programX
/usr/local/lib/programX

and is it possible?

thank you

What package type?
tar.gz?
RPM?
RPMs have a pre-determined install path usually.That's if you use a package manager.Command line use of RPM you can change the install path with the
--prefix <path> option,I believe.
Tar.gz or .tgz you put where you want,usually /usr/local/
lynch

Actually, I'm pretty sure that the standard is that you can do what you like under /usr/local (e.g. have /usr/local/mp3s if you wanted to share MP3s)

/usr/local/ do exactly the same that C:/program files/ in Windoze.
You're SUPPOSE to install all in this directory but If you do, you quickly loss yourself in your own computer

Create your own dir before it's too late

Well I hate to drag "Filesystem Hierarchy Standard" into this but if you want to be picky they should go under /opt.
OK, I love dragging LFS into it


3.12 /opt : Add-on application software packages
3.12.1 Purpose
/opt is reserved for the installation of add-on application software packages.

A package to be installed in /opt must locate its static files in a separate /opt/<package> directory tree, where <package> is a name that describes the software package.

3.12.2 Requirements

"/opt"
<package>
"Add-on application software packages"
Static package objects

Tree 3.12.2.1

The directories /opt/bin, /opt/doc, /opt/include, /opt/info, /opt/lib, and /opt/man are reserved for local system administrator use. Packages may provide "front-end" files intended to be placed in (by linking or copying) these reserved directories by the local system administrator, but must function normally in the absence of these reserved directories.

Programs to be invoked by users must be located in the directory /opt/<package>/bin. If the package includes UNIX manual pages, they must be located in /opt/<package>/man and the same substructure as /usr/share/man must be used.

Package files that are variable (change in normal operation) must be installed in /var/opt. See the section on /var/opt for more information.

Host-specific configuration files must be installed in /etc/opt. See the section on /etc for more information.

No other package files may exist outside the /opt, /var/opt, and /etc/opt hierarchies except for those package files that must reside in specific locations within the filesystem tree in order to function properly. For example, device lock files must be placed in /var/lock and devices must be located in /dev.

Distributions may install software in /opt, but must not modify or delete software installed by the local system administrator without the assent of the local system administrator.
BEGIN RATIONALE

When it comes to "standards", they are only as good as the extent to which they are adopted .

The best thing to do is install a package where it wants to go, and follow any "read me" files looking for path problems and the like.

The alternative is to spend the rest of your life playing with your system instead of using it, and trying to follow any number of evolving standards instead of enjoying your Linux freedom. You need to figure out who is the master and what is the tool !!

I couldn't agree more about "Linux freedom"

Although I describe Unix as an OS designed by committe .....the problem is the committe never met

!!

Linux was intended to be OS for developers designed by developers!!!
As far as freedom concerned, some ppl only see free part of it and it sounds for them as in beer.
:-)

pickledbeens I guess the comment about FHS was about us getting into discussion some time earlier, oh well it still exists and if you don't build LFS your initial setup is FHS compatible even if you use Solaris.

Your comment about intended use of Linux, applays to Unix in gerneral, iti wasn't developed as a commerical product at ATT

My final comment (for now) about LHS comes directory from the soruce:

Filesystem Hierarchy Standard
3.12 /opt : Add-on application software packages
3.12.1 Purpose
/opt is reserved for the installation of add-on application software packages.

A package to be installed in /opt must locate its static files in a separate /opt/<package> directory tree, where <package> is a name that describes the software package.

3.12.2 Requirements

"/opt"
<package>
"Add-on application software packages"
Static package objects

Tree 3.12.2.1

The directories /opt/bin, /opt/doc, /opt/include, /opt/info, /opt/lib, and /opt/man are reserved for local system administrator use. Packages may provide "front-end" files intended to be placed in (by linking or copying) these reserved directories by the local system administrator, but must function normally in the absence of these reserved directories.

Programs to be invoked by users must be located in the directory /opt/<package>/bin. If the package includes UNIX manual pages, they must be located in /opt/<package>/man and the same substructure as /usr/share/man must be used.

Package files that are variable (change in normal operation) must be installed in /var/opt. See the section on /var/opt for more information.

Host-specific configuration files must be installed in /etc/opt. See the section on /etc for more information.

No other package files may exist outside the /opt, /var/opt, and /etc/opt hierarchies except for those package files that must reside in specific locations within the filesystem tree in order to function properly. For example, device lock files must be placed in /var/lock and devices must be located in /dev.

Distributions may install software in /opt, but must not modify or delete software installed by the local system administrator without the assent of the local system administrator.
BEGIN RATIONALE



Now I ask you based on this definition are apps that Apache, MySQL [opt]ional? If so where should they be installed? Optional meaning not required fo the operation of the OS?

As far as Solaris goes the clients I have've support, have alway placed apps like Oracle under their own directory struction. And the same goes for "site specific application"

i don't have /opt/lib /opt/share /opt/include

by the way
i think i read somewhere
/usr/local is reserved for the installation of add-on application software packages.
is this wrong?


anyway, back to the original question,
i prefer clean install when i upgrade mandrake,
that means i have to give up /usr directory (but not /usr/local)
so if i could force programs to install files under
/usr/local/lib/a-program/
/usr/local/share/a-program/
along with /usr/local/a-program/

or
/opt/lib
/opt/share?


or my whole idea with this is wrong?

sorry for same question again and again..

thx

That LHS wasn't directed at you
The only way to specify a app extension for each directory
you have to set each flag during the ./configure.

./configure --help |less

Install where you want, programs will not complain anyway

But still... If I type "ls" in /usr/local/ directory, I have 3 pages of result and this system is only 7 months old

So I think it's better to install progs where you want.
My new linux box has /lib, /progs, /test and /others directorys