From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Localization files in /usr/lib/locale
Date: Wed, 30 Dec 2020 17:17:19 +0100 [thread overview]
Message-ID: <20201230161719.jxBHEdGNXzgqjPx_SgN578Ze_0F-o9KFaXKcyHH39mc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27491@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 466 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/issues/27491#issuecomment-752677658
Comment:
the m4 files causing this should be fixed either way since they may be used for user built stuff and we don't want that in there either
and then for packages we need to fix it on per-package basis (I see no other way) and introduce a pkglint check to add /usr/lib/locale into forbidden directories (except for glibc-locales)
next prev parent reply other threads:[~2020-12-30 16:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 4:47 [ISSUE] " ericonr
2020-12-28 9:04 ` newbluemoon
2020-12-28 9:08 ` newbluemoon
2020-12-28 9:25 ` newbluemoon
2020-12-28 13:56 ` sgn
2020-12-28 13:56 ` sgn
2020-12-28 16:15 ` ericonr
2020-12-28 16:58 ` newbluemoon
2020-12-28 18:26 ` ericonr
2020-12-28 18:56 ` newbluemoon
2020-12-28 22:05 ` q66
2020-12-30 15:45 ` sgn
2020-12-30 15:49 ` sgn
2020-12-30 15:52 ` newbluemoon
2020-12-30 16:17 ` q66 [this message]
2020-12-30 16:22 ` sgn
2020-12-30 17:18 ` q66
2020-12-30 17:18 ` q66
2020-12-31 0:48 ` sgn
2020-12-31 5:46 ` ericonr
2020-12-31 11:04 ` sgn
2020-12-31 11:05 ` sgn
2020-12-31 11:52 ` sgn
2020-12-31 11:54 ` q66
2020-12-31 11:57 ` q66
2021-04-03 8:08 ` Justinizer
2021-06-15 15:00 ` sgn
2021-06-15 15:14 ` ericonr
2021-06-15 15:16 ` ericonr
2022-05-01 2:14 ` github-actions
2022-05-16 2:07 ` [ISSUE] [CLOSED] " github-actions
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=20201230161719.jxBHEdGNXzgqjPx_SgN578Ze_0F-o9KFaXKcyHH39mc@z \
--to=q66@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).