diff options
Diffstat (limited to '_sources/installed-files.rst.txt')
| -rw-r--r-- | _sources/installed-files.rst.txt | 28 |
1 files changed, 28 insertions, 0 deletions
diff --git a/_sources/installed-files.rst.txt b/_sources/installed-files.rst.txt index 1468288..6ccc1be 100644 --- a/_sources/installed-files.rst.txt +++ b/_sources/installed-files.rst.txt @@ -57,6 +57,14 @@ really necessary (e.g. for recovery tools) but otherwise proliferating it is considered harmful. There is no point in installing static libraries if they are never going to be used. +.. Note:: + + If the package's build system does not support disabling static + library build, it is recommended to patch it and submit the patch + upstream. However, if that is not feasible and building both shared + and static libraries does not require compiling source files twice, + it is acceptable to strip static libraries in ``src_install()``. + .. index:: pair: installed files; libtool file @@ -106,3 +114,23 @@ an empty installation image. Package managers rely on this for some optimizations. Also QA tools make certain assumptions about virtuals, e.g., that they must not assign the ``LICENSE`` variable (which would be impossible if they installed any files). + + +.. index:: + pair: installed files; manpages + +Installation of manpages +------------------------ +:PG: 0305 +:Source: QA +:Reported: no + +Packages must not disable installing manpages via USE flags (e.g. +``USE=man`` or ``USE=doc``). If upstream does not ship prebuilt +manpages and building them requires additional dependencies, +the maintainer should build them and ship along with the package. + +*Rationale*: Manpages are basic documentation for installed software. +While additional dependencies are inconvenient for users, not building +manpages is harmful. Including (optionally or unconditionally) +prebuilt manpages is a good compromise. |