I agree completely with Gar.
Personally, for all debs/rpms I build I would tend to use system locations (/etc/appname, /var/log/, etc.) but for my own non-packaged stuff or apps I download and build from source I use /opt/appame/x.y.z/...
I like being able to rm -rf /opt/appname or rm -rf /opt/appname/specific-version
Only messy bit is symlinks into /etc/rc* for sysv init ot upstart etc.
Personally I dislike /usr/local for all but trivial tools in /usr/local/bin..
From: Gareth 'bigbro' Eason <bigbro at skynet.ie>
Sent: 12 May 2010 22:01
To: ilug at linux.ie
Subject: Re: [ILUG] Application Locations
-----BEGIN PGP SIGNED MESSAGE-----
On 12/05/10 17:38, Rory Browne wrote:
> Sorry - forgot to cc ilug.
>> On 12 May 2010 17:37, Rory Browne <rbmlist at gmail.com> wrote:
>> Personally if it was a commercial app, meant to live in it's own
>> little sandbox/world, I'd put everything under /usr/local/appname
>>>> In your case, I'd put
>>>> executables in /usr/local/killerapp/bin
>> config in /usr/local/killerapp/etc, or /usr/local/killerapp/conf (
As the discussion shows, it depends. The FHS (File System Hierarchy)
certainly helps but as you also pointed out, different distros seem to
have their own conventions.
If the app is closed source and relatively self contained, I'd suggest
putting it in /opt. So:
/opt/killerapp/bin - binaries
/opt/killerapp/etc - shared /default config
/opt/killerapp/lib - libraries (there are good arguments as to why you
might want to put these in /usr/lib too...)
/home/$USER/.config/killerapp - user specific configuration. Again, good
arguments that you could use /home/$USER/.killerapp/
If killerapp is something that runs more systemwide, then there are
good arguments that you should use /etc/defaults/killerapp to store
default config and /etc/killerapp/ to store running config. This is
particularly relevant if a daemon is involved (and should include a
/etc/init.d/killerapp script complying with the standard protocols for
same too, please :)
The main thing is to pick one standard - I particularly like the idea
of having everything self-contained under /opt, but if you make a .deb
or .rpm then it matters a lot less since maagement of the files can be
done sanely with the package management system :)
Hope this helps.
Ob. disclaimer: All the above is merely my opinion. There are other
opinions which are undoubtedly equally and/or more right than mine :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
[The entire original message is not included]
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!