man uses less as the default pager. (The mdocml package has less as a dependency so less should always be installed with man on a Void Linux system)
Actual behavior
man uses more as the default pager.
Steps to reproduce the behavior
check out latest version of void-packages repo
crossbuild mdocml (for instance with ./xbps-src -a armv5tel-musl pkg mdocml
install mdocml on target device
open a man page (for instance man man)
Notes
I think this happens because although less is a build dependency of mdocml, the configure script for mandoc tries to run less to check whether it is present, but the cross version gets installed in usr/arm-linux-musleabi/bin, which isn't in PATH (and probably wouldn't run anyway being a non-native binary).
I figured out what was going on by running xbps-src -a armv5tel-musl configure mdocml, and looking at masterdir/builddir/mandoc*/config.log. I also verified that the same thing happened when cross-compiling for different targets (and different architectures).
I'm not sure of the right way to fix this, setting BINM_PAGER in configure.local would probably do the job, but maybe there is a more standard way of fixing this sort of problem?
System
xuname: Void 5.15.41_1 x86_64-musl GenuineIntel notuptodate rFFFF
package: mdocml-1.14.6_3
Expected behavior
man
usesless
as the default pager. (The mdocml package has less as a dependency so less should always be installed with man on a Void Linux system)Actual behavior
man
usesmore
as the default pager.Steps to reproduce the behavior
./xbps-src -a armv5tel-musl pkg mdocml
man man
)Notes
I think this happens because although less is a build dependency of mdocml, the configure script for mandoc tries to run less to check whether it is present, but the cross version gets installed in
usr/arm-linux-musleabi/bin
, which isn't in PATH (and probably wouldn't run anyway being a non-native binary).I figured out what was going on by running
xbps-src -a armv5tel-musl configure mdocml
, and looking atmasterdir/builddir/mandoc*/config.log
. I also verified that the same thing happened when cross-compiling for different targets (and different architectures).I'm not sure of the right way to fix this, setting
BINM_PAGER
inconfigure.local
would probably do the job, but maybe there is a more standard way of fixing this sort of problem?