lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170420155044.0b87fc2d@lwn.net>
Date:   Thu, 20 Apr 2017 15:50:44 -0600
From:   Jonathan Corbet <corbet@....net>
To:     "Herton R. Krzesinski" <herton@...hat.com>
Cc:     linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Documentation: allow installing man pages to a user
 defined directory

On Thu, 20 Apr 2017 15:57:28 -0300
"Herton R. Krzesinski" <herton@...hat.com> wrote:

> Documentation/DocBook/Makefile hard codes the prefixed path to which you
> can install the built man pages (/usr/local prefix). That's unfortunate
> since the user may want to install to another prefix or location (for
> example, a distribution packaging the man pages may want to install to a
> random temporary location in the build process).
> 
> Be flexible and allow the prefixed path to which we install man pages to be
> changed with the INSTALL_MAN_PATH environment variable (and use the same
> default as other similar variables like INSTALL_HDR_PATH).

Applied, thanks.

Of course, the DocBook-based man-page generation is fading away, and we
haven't managed to put together a replacement quite yet.  Soon, I hope...

jon

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ