git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org,  Eli Schwartz <eschwartz@gentoo.org>
Subject: Re: [PATCH] meson: fix perl dependencies for Documentation
Date: Tue, 14 Jan 2025 14:03:21 +0000	[thread overview]
Message-ID: <87r055wl06.fsf@gentoo.org> (raw)
In-Reply-To: <Z4TOTVZbDlxh4Uuy@pks.im> (Patrick Steinhardt's message of "Mon, 13 Jan 2025 09:26:59 +0100")

Patrick Steinhardt <ps@pks.im> writes:

> On Sat, Jan 11, 2025 at 06:38:50AM +0000, Sam James wrote:
>> diff --git a/Documentation/technical/meson.build b/Documentation/technical/meson.build
>> index 21dfb8b5c9..8c93da3566 100644
>> --- a/Documentation/technical/meson.build
>> +++ b/Documentation/technical/meson.build
>> @@ -42,6 +42,7 @@ api_index = custom_target(
>>      '@OUTPUT@',
>>    ],
>>    env: script_environment,
>> +  depends: documentation_deps,
>>    input: api_docs,
>>    output: 'api-index.txt',
>>  )
>
> Wait, this doesn't make a lot of sense to me. "api-index.sh" does not
> care about "asciidoc.conf" at all, so why is this dependency needed?

You're completely right -- I thought I'd found that api-index.sh *did*
need it, but it definitely doesn't upon checking.

>
>> @@ -60,6 +61,7 @@ foreach article : api_docs + articles
>>      command: asciidoc_html_options,
>>      input: article,
>>      output: fs.stem(article) + '.html',
>> +    depends: documentation_deps,
>>      install: true,
>>      install_dir: get_option('datadir') / 'doc/git-doc/technical',
>>    )
>
> This one looks as expected, though.
>
> Thanks!

I'll respin. Thanks.

>
> Patrick

      reply	other threads:[~2025-01-14 14:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-11  6:38 [PATCH] meson: fix perl dependencies for Documentation Sam James
2025-01-13  8:26 ` Patrick Steinhardt
2025-01-14 14:03   ` Sam James [this message]

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=87r055wl06.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=eschwartz@gentoo.org \
    --cc=git@vger.kernel.org \
    --cc=ps@pks.im \
    /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).