git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: "D. Ben Knoble" <ben.knoble+github@gmail.com>,
	git@vger.kernel.org, Todd Zullinger <tmz@pobox.com>
Subject: Re: [PATCH] meson: make GIT_HTML_PATH configurable
Date: Thu, 6 Nov 2025 08:51:06 +0100	[thread overview]
Message-ID: <aQxTatYlnSJwNjta@pks.im> (raw)
In-Reply-To: <xmqqms51rhbx.fsf@gitster.g>

On Tue, Nov 04, 2025 at 06:41:06AM -0800, Junio C Hamano wrote:
> "D. Ben Knoble" <ben.knoble+github@gmail.com> writes:
> 
> > Makefile-based builds can configure Git's internal HTML_PATH by defining
> > htmldir, which is useful for packagers that put documentation in
> > different locations. Gentoo, for example, uses version-suffixed
> > directories like ${prefix}/share/doc/git-2.51 and puts the HTML
> > documentation in an 'html' subdirectory of the same.
> >
> > Propagate the same configuration knob to Meson-based builds so that
> > "git --html-path" on such systems can be configured to output the
> > correct directory.
> >
> > Signed-off-by: D. Ben Knoble <ben.knoble+github@gmail.com>
> > ---
> 
> Makes sense (a more meson-minded person needs to double check my
> knee-jerk reaction, though).  It is surprising that 
> 
>     $ git grep "dir', " meson_options.txt
>     meson_options.txt:option('perllibdir', type: 'string', value: '',
> 
> has only a single hit (now two), though.  I thought we have a lot
> more flexibility in our build process.

That was a concious decision when I introduced Meson. The discussion
back then was whether most of the build options that we have are even
used anywhere, so we eventually agreed to only add options on an
as-needed basis.

> I am also a bit surprised that these things are of type 'string'; I
> somehow was expecting that more modern build system would offer
> richer (relative to Makefile, that is) types like 'filename' or
> 'path'.

Meson provides tools to handle paths nicely [1], but it ultimately ends
up using strings indeed.

[1]: https://mesonbuild.com/Fs-module.html

Patrick

  parent reply	other threads:[~2025-11-06  7:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04 13:58 [PATCH] meson: make GIT_HTML_PATH configurable D. Ben Knoble
2025-11-04 14:41 ` Junio C Hamano
2025-11-04 16:47   ` Ben Knoble
2025-11-06  7:51   ` Patrick Steinhardt [this message]
2025-11-06  7:51 ` Patrick Steinhardt
2025-11-06 14:08   ` Ben Knoble
2025-11-06 15:29     ` Junio C Hamano
2025-11-11  0:25 ` D. Ben Knoble
2025-11-11 13:43   ` Karthik Nayak
2025-11-11 18:52     ` D. Ben Knoble

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aQxTatYlnSJwNjta@pks.im \
    --to=ps@pks.im \
    --cc=ben.knoble+github@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=tmz@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).