User:Suzanne.soy/Data storage: RFC


 * FreeCAD should honor the [ XDG https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html
 * for configuration files, i.e. most of
 * for any data that can be deleted and regenerated offline, and caches of things which normally require network access at the moment when they are browsed, so most likely and
 * for fonts, icons etc. which are usable by multiple applications. It is the equivalent of ( is  by default)
 * There are some recommendations about other directories namely (portable libraries)  (arch-specific libraries) and  (executable libraries) A few tools (1, 2) use the directories other than.
 * defaults to
 * It is unclear what the difference between and  is:
 * This page on tldp.org says that plug-ins live in ,
 * this page on tldp.org says that "The "share" word is used because what is under /usr/share is platform independent, and can be shared among several machines across a network filesystem",
 * this page at freedesktop.org says that is for "Static, private vendor data that is compatible with all architectures" and that  is for "Resources shared between multiple packages, such as fonts or artwork.".
 * The directories other than are not customizable using env vars.
 * Macros and mods (currently in and ), when they are installed by the Addon manager, should be in  or in.
 * Which one to pick depends on whether we consider these "plug-ins" usable by other tools or whether they are private (which could likely be understood as "FreeCAD-specific"). Branded versions of FreeCAD can share installed macros and mods; and external applications could invoke FreeCAD macros directly (see e.g. how the XternalApps Workbench invokes Inkscape extensions from within FreeCAD, the reverse would also make sense). Also, since is not customizable, it seems less useful to move things there (maybe it is a recent

https://wiki.debian.org/XDGBaseDirectorySpecification#state

/usr/share/freecad/mod

, ~/.local/share/freecad/freecad/freecad.qhc


 * as the default location when opening/saving files on a fresh installation (probably already the case, I didn't pay attention; the is probably an okay choice especially when started from the command-line)