From: DJ Delorie <dj@redhat.com>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: libc-alpha@sourceware.org, fweimer@redhat.com
Subject: Re: [PATCH 2/2] localedata: Do not generate output if warnings were present.
Date: Mon, 07 Feb 2022 22:51:01 -0500 [thread overview]
Message-ID: <xna6f2vwwq.fsf@greed.delorie.com> (raw)
In-Reply-To: <20220205025700.3728228-3-carlos@redhat.com> (libc-alpha@sourceware.org)
"Carlos O'Donell via Libc-alpha" <libc-alpha@sourceware.org> writes:
> diff --git a/localedata/Makefile b/localedata/Makefile
> $(INSTALL-SUPPORTED-LOCALE-ARCHIVE): install-locales-dir
> - @flags="-c"; \
> $(build-one-locale)
Ok. (or do we set this to "" ?)
> $(INSTALL-SUPPORTED-LOCALE-FILES): install-locales-dir
> - @flags="-c --no-archive --no-hard-links"; \
> + @flags="--no-archive --no-hard-links"; \
> $(build-one-locale)
Ok.
> diff --git a/localedata/gen-locale.sh b/localedata/gen-locale.sh
> -# Run quietly and force output.
> -flags="--quiet -c"
> +# Do not force output with '-c', all locales should compile without
> +# warning or errors. There is likewise no need to run quietly with
> +# '--quiet' since all locales should compile without additional
> +# diagnostics. If there are messages printed then we want to see
> +# them, fix them, and the associated error or warning. During
> +# development it may be beneficialy to put '--quiet -c' here to allow
> +# you to develop in-progress locales.
> +flags=""
Ok, but this assumes that all locales are fully defined, with no fields
left to their defaults.
LGTM
Reviewed-by: DJ Delorie <dj@redhat.com>
next prev parent reply other threads:[~2022-02-08 3:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 2:56 [PATCH 0/2] Improve LC_MONETARY handling Carlos O'Donell
2022-02-05 2:56 ` [PATCH 1/2] localedef: Update LC_MONETARY handling (Bug 28845) Carlos O'Donell
2022-02-08 3:46 ` DJ Delorie
2022-02-17 14:51 ` Andreas Schwab
2022-02-05 2:57 ` [PATCH 2/2] localedata: Do not generate output if warnings were present Carlos O'Donell
2022-02-08 3:51 ` DJ Delorie [this message]
2022-02-17 14:52 ` Andreas Schwab
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=xna6f2vwwq.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).