From a197da707cc46e52ed2ba86b7965a9b16444093f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Johannes=20L=C3=B6thberg?= Date: Tue, 29 Aug 2017 19:27:50 +0200 Subject: [PATCH 2/3] basedir: document ~/.local/bin --- basedir/basedir-spec.xml | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/basedir/basedir-spec.xml b/basedir/basedir-spec.xml index eefbe2b..305229c 100644 --- a/basedir/basedir-spec.xml +++ b/basedir/basedir-spec.xml @@ -34,6 +34,15 @@ + + Johannes + Löthberg + +
+ johannes@kyriasis.com +
+
+
@@ -66,6 +75,12 @@ environment variable $XDG_CONFIG_HOME. + + + There is a single base directory relative to which + user-specific executable files may be written. + + There is a set of preference ordered base directories relative to @@ -122,6 +137,21 @@ $XDG_CONFIG_HOME is either not set or empty, a default equal to $HOME/.config should be used. + + User-specific executable files may be stored in + $HOME/.local/bin. Distributions should ensure + this directory shows up in the UNIX $PATH + environment variable, at an appropriate place. + + + Since $HOME might be shared between systems + of different achitectures, installing compiled binaries to + $HOME/.local/bin could cause + problems when used on systems of differing architectures. This + is often not a problem, but the fact that + $HOME becomes partially achitecture-specific + if compiled binaries are placed in it should be kept in mind. + $XDG_DATA_DIRS defines the preference-ordered set of base directories to search for data files in addition to the -- 2.17.0