bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: Gavin Smith <gavinsmith0123@gmail.com>
Subject: Re: gperf dependency not documented
Date: Sat, 24 Feb 2024 00:56:50 +0100	[thread overview]
Message-ID: <5445983.X9hSmTKtgW@nimes> (raw)
In-Reply-To: <ZdeBlMAnWtr0kKCQ@beigestar>

Gavin Smith wrote:
> The DEPENDENCIES file in gnulib states a module that depends on the gperf
> program:
> * GNU gperf 3.0.1 or newer.
>   + 3.0.1 or newer is mandatory, but 3.1 or newer is recommended.
>     Needed if you use the 'iconv_open' module.
> However, it is not the only module that uses this program.  gperf is
> also listed as a dependency of the following modules:
> unicase/locale-language
> unicase/special-casing
> uninorm/composition
> unictype/joiningtype-byname
> unictype/category-byname
> unictype/combining-class-byname
> unictype/property-byname
> unictype/joininggroup-byname
> unictype/incb-byname
> unictype/bidiclass-byname
> unictype/scripts
> Should these be added to DEPENDENCIES?

Thanks for the investigation. I'm updating this entry:

2024-02-23  Bruno Haible  <bruno@clisp.org>

	DEPENDENCIES: Update entry about gperf.
	Reported by Gavin Smith <gavinsmith0123@gmail.com> in
	* DEPENDENCIES (gperf): Mention some more modules which require 'gperf'.

index 3b24f45ad6..e396adbd80 100644
@@ -135,7 +135,8 @@ at any time.
 * GNU gperf 3.0.1 or newer.
   + 3.0.1 or newer is mandatory, but 3.1 or newer is recommended.
-    Needed if you use the 'iconv_open' module.
+    Needed if you use the 'iconv_open' module or some of the
+    unictype/*, unicase/*, uninorm/* modules.
   + Homepage:
   + Download:

      reply	other threads:[~2024-02-23 23:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22 17:17 gperf dependency not documented Gavin Smith
2024-02-23 23:56 ` Bruno Haible [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:

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

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

  git send-email \
    --in-reply-to=5445983.X9hSmTKtgW@nimes \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=gavinsmith0123@gmail.com \


* 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).