On 13.11.25 20:58, Andrew Cooper wrote:
On 13/11/2025 5:02 pm, Jan Beulich wrote:
On 13.11.2025 17:59, Jan Beulich wrote:
On 11.11.2025 17:19, Juergen Gross wrote:
--- a/config/Paths.mk.in
+++ b/config/Paths.mk.in
@@ -20,10 +20,7 @@ libexecdir               := @libexecdir@
  datarootdir              := @datarootdir@
  mandir                   := @mandir@
  docdir                   := @docdir@
-dvidir                   := @dvidir@
  htmldir                  := @htmldir@
-pdfdir                   := @pdfdir@
Question is whether we're mistakenly not respecting in particular this one,
for the *.pdf we create. For all the others I agree there's no (present or
potential) use. I notice though that docs/Makefile cleans e.g. *.dvi
nevertheless.
Actually, I can't spot a use of htmldir either, when likely we should respect
that one, too.

Besides the manpages, nothing generated in docs/ is really fit to
package for end users.  There's no coherent structure, some of it is
straight braindumps from developers.

docdir is only used by the {un,}install-html targets (opencoding
htmldir), and the rm in the install target is further evidence to the
unsuitability of what's there.

I'd go so far as to suggest we should drop install-html, except that it
would break the generation of https://xenbits.xen.org/docs/unstable/

I think I'll leave further cleanup for another patch.

As you said, docdir is being used right now and htmldir could be used in
case the open coding via docdir is being cleaned up.


Juergen

Attachment: OpenPGP_0xB0DE9DD628BF132F.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to