From: Eli Zaretskii <eliz@gnu.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: luangruo@yahoo.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: `--with-small-ja-dic`
Date: Thu, 15 Feb 2024 12:16:21 +0200 [thread overview]
Message-ID: <86eddevxqi.fsf@gnu.org> (raw)
In-Reply-To: <ufrxut967@gentoo.org> (message from Ulrich Mueller on Thu, 15 Feb 2024 09:37:36 +0100)
> From: Ulrich Mueller <ulm@gentoo.org>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
> Date: Thu, 15 Feb 2024 09:37:36 +0100
>
> I wonder if the option couldn't be replaced by another one like
> --without-ja-dic? That would reduce both the installation footprint
> and the compile time.
>
> Rationale is that Japanese users may prefer the large file, but users
> who don't speak Japanese don't need the file at all.
How is this different from any other dictionary we produce as part of
the build? E.g., ZIRANMA is also large.
Users who are bothered by files in the distribution they don't need
can simply delete them. Or the downstream distros could provide more
fine-grained installation options. We here traditionally include in
the installation everything that some feature might need, and I don't
see any reason to change that policy, except (perhaps) when we find a
way to keep some of the stuff on ELPA.
next prev parent reply other threads:[~2024-02-15 10:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 22:32 `--with-small-ja-dic` Stefan Monnier
2024-02-15 1:36 ` `--with-small-ja-dic` Po Lu
2024-02-15 2:45 ` `--with-small-ja-dic` Stefan Monnier
2024-02-15 5:30 ` `--with-small-ja-dic` Po Lu
2024-02-15 8:37 ` `--with-small-ja-dic` Ulrich Mueller
2024-02-15 10:16 ` Eli Zaretskii [this message]
2024-02-15 13:11 ` `--with-small-ja-dic` Ulrich Mueller
2024-02-15 13:57 ` `--with-small-ja-dic` Eli Zaretskii
2024-02-15 6:47 ` `--with-small-ja-dic` Eli Zaretskii
2024-02-15 14:13 ` `--with-small-ja-dic` Stefan Monnier
2024-02-15 16:34 ` `--with-small-ja-dic` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86eddevxqi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=monnier@iro.umontreal.ca \
--cc=ulm@gentoo.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).