From: waltdnes@waltdnes.org
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] How to deal with LINGUAS mess?
Date: Sun, 29 May 2016 22:21:53 -0400 [thread overview]
Message-ID: <20160530022153.GA17051@waltdnes.org> (raw)
In-Reply-To: <20160529145803.059f1a20.mgorny@gentoo.org>
On Sun, May 29, 2016 at 02:58:03PM +0200, Micha?? Górny wrote
> On Sat, 21 May 2016 11:19:07 -0400
> waltdnes@waltdnes.org wrote:
>
> > 5. An reversed variant of INSTALL_MASK in make.conf, e.g.
> > LOCALE_ALLOW="foo bar fubar"
> >
> > which would block installing files in /usr/share/locale/* and
> > /usr/share/man/* EXCEPT for...
> >
> > /usr/share/locale/foo
> > /usr/share/locale/bar
> > /usr/share/locale/fubar
> > /usr/share/man/foo
> > /usr/share/man/bar
> > /usr/share/man/fubar
>
> This can be accomplished using inclusion/exclusion logic included in
> the patches I've recently sent for Portage.
>
> INSTALL_MASK="/usr/share/locale -/usr/share/locale/foo"
Thanks. localepurge cleans up after the fact. Your patches would
prevent the problem in the first place, which is a better approach. It
also handles systemd files and can be used when some new stuff comes up
in future that we haven't thought of yet.
--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
next prev parent reply other threads:[~2016-05-30 2:22 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 ` [gentoo-dev] " Michael Orlitzky
2016-05-21 15:19 ` 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 [this message]
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=20160530022153.GA17051@waltdnes.org \
--to=waltdnes@waltdnes.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