public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Possible merge of myspell/hunspell dictionaries
Date: Sun, 09 Jul 2023 10:10:34 +0100	[thread overview]
Message-ID: <87edlhe9ed.fsf@gentoo.org> (raw)
In-Reply-To: <B1CFDF17-2C11-47AA-AEB6-6FF4026D83A8@gmail.com>


zurabid2016@gmail.com writes:

> Hello everyone,
>
> I am new here, so I'm sorry in advance for any stupid thing I may
> say. I want to adopt hunspell for various reasons and what I've
> noticed is a plethora of app-dicts/myspell-* packages (for each
> language there's one).
>
> I suggest merging them into one big myspell-dicts package, which will certainly reduce maintenance burden (the similar thing is done with libreoffice-l10n, I think).
>

My only real question is why they're split in the first place and
if there's some good reason for that. I've no idea.

> Looking forward to hearing your thoughts about my proposal
>

I think you sent this email a few days ago, fwiw, see
https://marc.info/?l=gentoo-dev&m=168872367517846&w=2.

I'd maybe ask on IRC at #gentoo-dev-help & #gentoo-proxy-maint,
as well, where we're focused on helping new contributors.

I'd feel a bit better about the merge, I suppose, if I knew
someone had checked git history and see if anyone suggested
it before on Bugzilla and such.

Anyway, it doesn't sound like a crazy idea prima facie.

best,
sam


  reply	other threads:[~2023-07-09  9:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-09  8:55 [gentoo-dev] Possible merge of myspell/hunspell dictionaries zurabid2016
2023-07-09  9:10 ` Sam James [this message]
2023-07-09 10:10   ` Mart Raudsepp
2023-07-09 11:15     ` Ulrich Mueller
2023-07-12 19:10 ` [gentoo-dev] " Zurab Kvachadze
  -- strict thread matches above, loose matches on Subject: below --
2023-07-07  9:55 [gentoo-dev] " Zurab Kvachadze
2023-07-11  4:36 ` Joonas Niilola
2023-07-11  7:00   ` Ulrich Mueller

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=87edlhe9ed.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=gentoo-dev@lists.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox