Update Archivematica to obey the FHS
|Google Code Legacy ID:||Requires documentation:|
Archivematica should install files according to the Filesystem Hierarchy Standard. http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard
#2 Updated by Misty De Meo over 7 years ago
Archivematica should no longer install to /var/archivematica: http://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.html#PURPOSE31
Applications must generally not add directories to the top level of /var. Such directories should only be added if they have some system-wide implication, and in consultation with the FHS mailing list.
#3 Updated by Misty De Meo over 7 years ago
/var/archivematica should be in a subdirectory of /var (eg spool, local
/var/local would be inappropriate; it's documented as being for data in /usr/local.
We would probably need to break up parts of /var/archivematica into different locations.
- Processing directories (for instance watched directories) should likely go into /var/spool: http://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.html#VARSPOOLAPPLICATIONSPOOLDATA
/var/spool contains data which is awaiting some kind of later processing. Data in /var/spool represents work to be done in the future (by a program, user, or administrator)
- Other transient files should go in /var/lib? http://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.html#VARLIBVARIABLESTATEINFORMATION
State information is generally used to preserve the condition of an application (or a group of inter-related applications) between invocations and between different instances of the same application. State information should generally remain valid after a reboot, should not be logging output, and should not be spooled data.