public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joonas Niilola <juippis@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Possible merge of myspell/hunspell dictionaries
Date: Tue, 11 Jul 2023 07:36:44 +0300	[thread overview]
Message-ID: <0ced4ba0-d159-188a-b504-6a637b31f07f@gentoo.org> (raw)
In-Reply-To: <4c1518d9-ceb2-80f2-ff19-5f9646dd9f1a@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 969 bytes --]

On 7.7.2023 12.55, Zurab Kvachadze wrote:
> 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).
> 
> Looking forward to hearing your thoughts about my proposal
> 
> 
> — Obligatory footer —
> 
> BalkanMadman
> 
> 

Hey,

it would be better than the current situation for sure, but my
impression with myspell* packages is that they all have different
version releases and different upstream source uris, so just wondering
can it be done with a single package? In theory it'd be an improvement
though if there is a single upstream holding all language options.

-- juippis

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

  reply	other threads:[~2023-07-11  4:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07  9:55 [gentoo-dev] Possible merge of myspell/hunspell dictionaries Zurab Kvachadze
2023-07-11  4:36 ` Joonas Niilola [this message]
2023-07-11  7:00   ` Ulrich Mueller
  -- strict thread matches above, loose matches on Subject: below --
2023-07-09  8:55 zurabid2016
2023-07-09  9:10 ` Sam James
2023-07-09 10:10   ` Mart Raudsepp
2023-07-09 11:15     ` 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=0ced4ba0-d159-188a-b504-6a637b31f07f@gentoo.org \
    --to=juippis@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