From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Getting rid of USE=unicode
Date: Wed, 30 Dec 2020 19:46:44 +0200 [thread overview]
Message-ID: <4133533.UPlyArG6xL@noumea> (raw)
[-- Attachment #1: Type: text/plain, Size: 608 bytes --]
Hi all,
since utf8 encoding is everywhere by now, and since switching the useflag
unicode off without taking precautions is a way to hose your installation, I
would propose to medium-term get rid of this flag.
Suggestion:
1) use.force unicode now/soon in the default profiles
2) step by step, modify ebuilds to enable the functionality unconditionally
(and if necessary fix depstrings)
3) at some point the flag is gone
Opinions?
Cheers,
Andreas
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, qa, toolchain, base-system, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2020-12-30 17:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 17:46 Andreas K. Huettel [this message]
2020-12-30 17:53 ` [gentoo-dev] Getting rid of USE=unicode Aisha Tammy
2020-12-30 18:34 ` Andreas K. Huettel
2020-12-30 23:17 ` Aisha Tammy
2020-12-31 1:16 ` James Cloos
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=4133533.UPlyArG6xL@noumea \
--to=dilfridge@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