public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] How to deal with LINGUAS mess?
Date: Sat, 21 May 2016 08:20:38 -0400	[thread overview]
Message-ID: <57405296.1090506@gentoo.org> (raw)
In-Reply-To: <20160521094128.0a7c7766.mgorny@gentoo.org>

On 05/21/2016 03:41 AM, Michał Górny wrote:
> 
> I see the following possibilities:
> 

#2 is ugly and requires a special case due to a bad choice of variable
name; #4 will never work.


> 3. We remove LINGUAS from USE_EXPAND and stop using it. If ebuilds have
> a good reason to use flags for localization, we introduce a new,
> non-colliding USE_EXPAND for that. We also ask users to replace LINGUAS
> with the new flag in their make.conf files. LINGUAS gets the original
> upstream behavior back, and we eventually discourage it in favor of new
> INSTALL_MASK features (WiP) [2].
> 

This is probably the best option because it fixes the real problem: we
tried to repurpose somebody else's environment variable for our package
manager. If we try to keep the name "LINGUAS", we may run into some
other problem down the line.


> 1. We start explicitly listing linguas_* in all ebuilds, no matter how
> tiny they are. Maintainers are required to keep IUSE up-to-date
> and users are forced to rebuild a lot. This is also a QA violation
> in terms of invalid use of USE flags.

This isn't as bad as you make it sound... the rebuilds would happen once
on a revision bump. The QA violation (I'm guessing) is that USE flags
shouldn't be used to control the installation of small text files.

I prefer a looser interpretation of that rule: maintainers don't have to
waste their time and complicate their ebuilds with USE flags to control
the installation of small text files if they don't want to. Basically an
"it's OK to install systemd unit files unconditionally" rule. Or in
other words, the rule is "it's OK not to do it" rather than "it's not OK
to do it."

I think if someone /wants/ to have a bunch of logic controlling the
installation of localization files, that's fine. But, this option would
force everyone to do it in order to work around an unfortunate choice of
variable name. It also adds some eternal mental overhead in that we have
to collectively remember that LINGUAS is special somehow and teach that
to everyone.

For those reasons I think #3 is a better long-term solution.


  parent reply	other threads:[~2016-05-21 12:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-21  7:41 [gentoo-dev] [RFC] How to deal with LINGUAS mess? Michał Górny
2016-05-21  8:14 ` Kent Fredric
2016-05-29 12:30   ` Michał Górny
2016-05-21  9:00 ` [gentoo-dev] " Ulrich Mueller
2016-05-21  9:04   ` Kent Fredric
2016-05-21  9:32     ` Ulrich Mueller
2016-05-21 19:35   ` Michał Górny
2016-05-21 12:20 ` Michael Orlitzky [this message]
2016-05-21 15:19 ` [gentoo-dev] " waltdnes
2016-05-27  7:17   ` Mart Raudsepp
2016-05-29 13:03     ` Michał Górny
2016-05-29 12:58   ` Michał Górny
2016-05-30  2:21     ` waltdnes
2016-05-30 10:47     ` Andrew Savchenko

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=57405296.1090506@gentoo.org \
    --to=mjo@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