public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] configure: Fix summary for --disable-metadata
Date: Thu, 20 Jan 2022 14:20:05 +0100	[thread overview]
Message-ID: <YelhhSlDCnqt5nsV@pevik> (raw)
In-Reply-To: <20220120124023.17469-1-chrubis@suse.cz>

Hi Cyril,

> This changes the m4/ltp-docparse.m4 to skip the detection and sets the
> corresponding variables so that we get correct summary when the metadata
> are disable by users.

Reviewed-by: Petr Vorel <pvorel@suse.cz>

LGTM, I'm for applying this before release.

./configure --disable-metadata-pdf --disable-metadata-html
...
configure: metadata generation disabled
...
METADATA
metadata generator: detect
HTML metadata: no
PDF metadata: no

=> this case is not handled well. Output during configure ("metadata generation
disabled") is IMHO more descriptive than our summary - "detect" can be confusing
for people. We could further tweak configure.ac:

@@ -43,6 +43,9 @@ fi

 if test "x$enable_metadata_html" = xyes -o "x$enable_metadata_pdf" = xyes; then
        AX_PROG_PERL_MODULES(Cwd File::Basename JSON LWP::Simple)
+else
+       with_metadata=no
+       with_metadata_generator=none
 fi

---
=> would lead to:
METADATA
metadata generator: none
HTML metadata: no
PDF metadata: no

But instead of that I'd also adjusted the summary to print "metadata disabled"
to reflect the reality, i.e. apply also my patch
https://lore.kernel.org/ltp/20220114125513.895-1-pvorel@suse.cz/

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-01-20 13:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-20 12:40 [LTP] [PATCH] configure: Fix summary for --disable-metadata Cyril Hrubis
2022-01-20 13:20 ` Petr Vorel [this message]
2022-01-24 14:02   ` Petr Vorel

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=YelhhSlDCnqt5nsV@pevik \
    --to=pvorel@suse.cz \
    --cc=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    /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