public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: Mart Raudsepp <leio@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Possible merge of myspell/hunspell dictionaries
Date: Sun, 09 Jul 2023 13:15:59 +0200	[thread overview]
Message-ID: <uzg4572ts@gentoo.org> (raw)
In-Reply-To: <a076f547d4c6c06fbb6cee2083c4710c35f8049d.camel@gentoo.org> (Mart Raudsepp's message of "Sun, 09 Jul 2023 13:10:43 +0300")

[-- Attachment #1: Type: text/plain, Size: 1507 bytes --]

>>>>> On Sun, 09 Jul 2023, Mart Raudsepp wrote:

> Ühel kenal päeval, P, 09.07.2023 kell 10:10, kirjutas Sam James:
>> 
>> zurabid2016@gmail.com writes:
>> 
>> > 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.

> I would guess that they are different packages because they all have a
> different SRC_URI. Many to some libreoffice assets download location,
> but not all.
> Maybe they could all come from the same source in an updated packaging
> though, I don't know the background.

These are different packages because they have different upstreams,
versioning schemes, and release cycles. Since we tend to follow
upstream packaging, I'm not sure if combining them would make sense.

I'm also not sure if it would reduce maintenance burden. I maintain
app-i18n/man-pages-l10n, which gets way more frequent releases than the
formerly separate man-pages-* packages, with each version bump requiring
build and test for all supported languages instead of just one.

Ulrich

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]

  reply	other threads:[~2023-07-09 11:16 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
2023-07-09 10:10   ` Mart Raudsepp
2023-07-09 11:15     ` Ulrich Mueller [this message]
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=uzg4572ts@gentoo.org \
    --to=ulm@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=leio@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