At 2025-01-15T12:45:22-0700, Sam Hartman wrote: > Marvin> I have on a number of occasions used these man pages, and > Marvin> having them installed locally is very helpful. I would > Marvin> rather have the man pages installed without the additional > Marvin> documentation in libpam-doc. Why not (other than a trip > Marvin> through NEW) put them in a new binary package > Marvin> libpam-manpages (arch:all)? I would prefer recommends > Marvin> rather than suggests. > > Do you actually have a system on which you want these man pages and on > which the extra space of libpam-doc would be a problem? > > Unless there's a compelling need, my answer is that I don't understand > why manpages should be separated from other documentation in this > instance.
Don't we have dpkg filters for this sort of use case?
dpkg(1):
--path-exclude=glob‐pattern
--path-include=glob‐pattern
Set glob‐pattern as a path filter, either by excluding or re‐
including previously excluded paths matching the specified
patterns during install (since dpkg 1.15.8).
...
This can be used to remove all paths except some particular
ones; a typical case is:
--path-exclude=/usr/share/doc/*
--path-include=/usr/share/doc/*/copyright
...
Are we missing some mechanism that would integrate this well with apt?
Possibly some curated set of "profiles" for common applications, like
localization file stripping?[1]
Elimination of those and man pages have been considered low-hanging
fruit by producers of "minimal" variants of Debian for about as long as
there have been such things _as_ variants of Debian.
Regards,
Branden
[1] I looked at the following page but the approaches listed seemed
mostly ad hoc, atomistic, and crude.
https://wiki.debian.org/ReduceDebian
signature.asc
Description: PGP signature
