shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2025-02-02 09:47:03 +03:00
Code

man: rebreak lines in file-hierarchy(7) a bit

Browse Source 
(Does not change a single word, just rebreaks a bunch of paragraphs
matching our current line breaking rules)
This commit is contained in:
Lennart Poettering 2023-06-27 10:28:44 +02:00
parent b4d6bc63e6
commit fa1d34825a
1 changed files with 18 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

47
man/file-hierarchy.xml
View File

@ -505,13 +505,10 @@
<varlistentry> <varlistentry>
<term><filename>~/.cache/</filename></term> <term><filename>~/.cache/</filename></term>
<listitem><para>Persistent user cache data. User programs may <listitem><para>Persistent user cache data. User programs may place non-essential data in this
place non-essential data in this directory. Flushing this directory. Flushing this directory should have no effect on operation of programs, except for
directory should have no effect on operation of programs, increased runtimes necessary to rebuild these caches. If an application finds
except for increased runtimes necessary to rebuild these <varname>$XDG_CACHE_HOME</varname> set, it should use the directory specified in it instead of this
caches. If an application finds
<varname>$XDG_CACHE_HOME</varname> set, it should use the
directory specified in it instead of this
directory.</para></listitem> directory.</para></listitem>
</varlistentry> </varlistentry>
@ -527,44 +524,36 @@
<varlistentry> <varlistentry>
<term><filename>~/.local/bin/</filename></term> <term><filename>~/.local/bin/</filename></term>
<listitem><para>Executables that shall appear in the user's <listitem><para>Executables that shall appear in the user's <varname>$PATH</varname> search path. It
<varname>$PATH</varname> search path. It is recommended not to is recommended not to place executables in this directory that are not useful for invocation from a
place executables in this directory that are not useful for shell; these should be placed in a subdirectory of <filename>~/.local/lib/</filename> instead. Care
invocation from a shell; these should be placed in a should be taken when placing architecture-dependent binaries in this place, which might be
subdirectory of <filename>~/.local/lib/</filename> instead. problematic if the home directory is shared between multiple hosts with different
Care should be taken when placing architecture-dependent
binaries in this place, which might be problematic if the home
directory is shared between multiple hosts with different
architectures.</para></listitem> architectures.</para></listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term><filename>~/.local/lib/</filename></term> <term><filename>~/.local/lib/</filename></term>
<listitem><para>Static, private vendor data that is compatible <listitem><para>Static, private vendor data that is compatible with all
with all architectures.</para></listitem> architectures.</para></listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term><filename>~/.local/lib/<replaceable>arch-id</replaceable>/</filename></term> <term><filename>~/.local/lib/<replaceable>arch-id</replaceable>/</filename></term>
<listitem><para>Location for placing public dynamic libraries. <listitem><para>Location for placing public dynamic libraries. The architecture identifier to use is
The architecture identifier to use is defined on <ulink defined on <ulink url="https://wiki.debian.org/Multiarch/Tuples">Multiarch Architecture Specifiers
url="https://wiki.debian.org/Multiarch/Tuples">Multiarch (Tuples)</ulink> list.</para></listitem>
Architecture Specifiers (Tuples)</ulink>
list.</para></listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term><filename>~/.local/share/</filename></term> <term><filename>~/.local/share/</filename></term>
<listitem><para>Resources shared between multiple packages, <listitem><para>Resources shared between multiple packages, such as fonts or artwork. Usually, the
such as fonts or artwork. Usually, the precise location and precise location and format of files stored below this directory is subject to specifications that
format of files stored below this directory is subject to ensure interoperability. If an application finds <varname>$XDG_DATA_HOME</varname> set, it should use
specifications that ensure interoperability. If an application the directory specified in it instead of this directory.</para></listitem>
finds <varname>$XDG_DATA_HOME</varname> set, it should use the
directory specified in it instead of this
directory.</para></listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>