mjhjmtu

What are the "standards" -- should I put application (not just binary, but entire distribution) to /usr/local or /usr/local/share.

For example scala or weka -- it contains examples, binaries, libraries, and so on. So it would be

/usr/local/scala-2.9.1 

or

/usr/local/share/scala-2.9.1

Since I am the only admin it is not a big deal for me, but I prefer to using something which is widely used, not with my own customs.

Important: I am not asking about cases, where you should split app into /usr/local/bin, /usr/local/lib and so on. Rather I am asking about case when you have to keep one main directory for entire application.

I think /opt is more standard in this sort of context. The relevant section in the Filesystem Hierarchy Standard is quoted below.

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.

 Rationale The use of /opt for add-on software is a
well-established practice in the UNIX community. The System V
Application Binary Interface [AT&T 1990], based on the System V
Interface Definition (Third Edition), provides for an /opt structure
very similar to the one defined here.

The Intel Binary Compatibility Standard v. 2 (iBCS2) also provides a
similar structure for /opt.

Generally, all data required to support a package on a system must be
present within /opt/, including files intended to be copied
into /etc/opt/ and /var/opt/ as well as reserved
directories in /opt.

The minor restrictions on distributions using /opt are necessary
because conflicts are possible between distribution-installed and
locally-installed software, especially in the case of fixed pathnames
found in some binary software.

The structure of the directories below /opt/ is left up to
the packager of the software, though it is recommended that packages
are installed in /opt// and follow a similar
structure to the guidelines for /opt/package. A valid reason for
diverging from this structure is for support packages which may have
files installed in /opt//lib or /opt//bin.

You should only use /usr/local/share for files which are not specific to a particular architecture / OS version.

After that it's up to you whether you distribute the files between the existing subdirs of /usr/local or if you create a new dedicated directory in /usr/local (but the latter will not already exist on the executable PATH, the LD_LIBRARY_PATH, nor the MANPATH).

Have a look at the FHS

Until /opt became common, the usual place was /usr/local/lib/<package>.

When installing local applications, there are multiple options depending on how you want to access and update. Also should be noted that some methods look more like the system you already have and some are more ad-hoc. I would suggest that the "best" solutions are the ones that make things easier to manage.

I have split this answer based on the number of packages to make custom installs for. The splitting is based on my own experiences. These experiences weigh the time it takes to manage the packages and the risks of messing up something. I do not mean that I have the knowledge of common standards but mean this as a reference point to look when making the decision.

For only few packages,I would to put add-on packages in /opt, where they are out of the way of everything else so nothing can mess them up and they can mess something else up. This is the method I use on my NAS. This method however keeps the binaries off your PATH, so you will need to add them manually. This works well if there are only few packages to install, but becomes quite a mess if there are many.

Updating here is quite easy as you simply overwrite the directory.

Pros:

• simple


• fast to setup


• no chance at affecting other parts of the system


• uninstall is as easy as install

Cons:

• Becomes rather tedious if the number of packages to install is large


• Makes PATH look messy

For more than a few packages, I would recommend using the /usr/local/<your package> and sym-linking the executable from /usr/local/bin or /usr/local/sbin depending on if you need root privileges. This saves you from changing your PATH every time something new is added so the PATH stays clean. This is the method I use on my Arch laptop for all non-pacman packages and AUR packages.

Updating is done by overwriting the package directory and checking that the symlink is still valid and fixing if it isn't.

Pros

• Doesn't make PATH messy


• Doesn't affect the base system


• Still very simple to remove all add-ons and return to a clean base system

Cons:

• More work to setup


• Removing only one package has some searching to do

For many packages. As this isn't the case you are wanting I will keep it brief. I would recommend splitting the package into bin, lib,share, etc. and installing them to /usr/local. This is to keep the structure clean. You can also specify who can write where and more. For example you don't want people other than root modifying the executable.

Here the updating gets a little more tricky as you need to write to more than a single directory. I would recommend packaging the whole thing and letting the package manager handle the rest.

The share

The share directory itself is for architecture independent files as noted in Faheem's link and the architecture dependent files should go to lib, lib32, lib64, etc.