From 7c59acba5699c9c58090a7a738669669a7307023 Mon Sep 17 00:00:00 2001 From: V3n3RiX Date: Sat, 21 Aug 2021 23:14:26 +0100 Subject: gentoo resync : 21.08.2021 --- .../2021-08-18-uclibc-ng-retirement.en.txt | 20 +++++++++++ .../2021-08-19-mc-legacy-config-dirs.en.txt | 37 +++++++++++++++++++++ metadata/news/Manifest | 30 ++++++++--------- metadata/news/Manifest.files.gz | Bin 13663 -> 14023 bytes metadata/news/timestamp.chk | 2 +- metadata/news/timestamp.commit | 2 +- 6 files changed, 74 insertions(+), 17 deletions(-) create mode 100644 metadata/news/2021-08-18-uclibc-ng-retirement/2021-08-18-uclibc-ng-retirement.en.txt create mode 100644 metadata/news/2021-08-19-mc-legacy-config-dirs/2021-08-19-mc-legacy-config-dirs.en.txt (limited to 'metadata/news') diff --git a/metadata/news/2021-08-18-uclibc-ng-retirement/2021-08-18-uclibc-ng-retirement.en.txt b/metadata/news/2021-08-18-uclibc-ng-retirement/2021-08-18-uclibc-ng-retirement.en.txt new file mode 100644 index 000000000000..862ad2ec84aa --- /dev/null +++ b/metadata/news/2021-08-18-uclibc-ng-retirement/2021-08-18-uclibc-ng-retirement.en.txt @@ -0,0 +1,20 @@ +Title: uClibc-ng retirement on 2022-01-01 +Author: Anthony G. Basile +Posted: 2021-08-18 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Profile: default/linux/uclibc/* + +uClibc-ng is mostly abandoned upstream, and since my RFC in Jan 2021, +no one has volunteered to step up maintenance or expressed interest in +the uClibc-ng profiles. With this announcement we last-rite the "uclibc" +profiles, which will be removed on 2022-01-01. For parties interested in +an alternative libc, consider moving to musl, which is supported. + +Gentoo continues to wholeheartedly support musl and is focusing its +efforts in that area. + +Resources: +- https://wiki.gentoo.org/wiki/Project:Hardened_musl +- https://gitweb.gentoo.org/proj/musl.git/ (overlay for patches) +- #gentoo-hardened (IRC channel on irc.libera.chat) for support and discussion diff --git a/metadata/news/2021-08-19-mc-legacy-config-dirs/2021-08-19-mc-legacy-config-dirs.en.txt b/metadata/news/2021-08-19-mc-legacy-config-dirs/2021-08-19-mc-legacy-config-dirs.en.txt new file mode 100644 index 000000000000..fe7d6ce15b61 --- /dev/null +++ b/metadata/news/2021-08-19-mc-legacy-config-dirs/2021-08-19-mc-legacy-config-dirs.en.txt @@ -0,0 +1,37 @@ +Title: >=app-misc/mc-4.8.27 to drop support for ~/.mc +Author: Marek Szuba +Posted: 2021-08-19 +Revision: 1 +News-Item-Format: 2.0 +Display-If-Installed: app-misc/mc + +app-misc/mc versions between 4.8.1 and 4.8.26, inclusive, would look +for their user configuration in two possible places: + + * if built with USE=-xdg, only the legacy directory ~/.mc is used; + + * if built with USE=xdg, mc uses appropriate XDG user directories + (e.g. ~/.config/mc, ~/.local/share/mc) if present and attempts + to automatically migrate the contents of ~/.mc otherwise. + +However, starting with version 4.8.27 Midnight Commander will use _only +XDG user directories_ for its configuration and no longer automatically +migrate the contents of ~/.mc. For more information, see: + + https://midnight-commander.org/wiki/NEWS-4.8.27 + https://midnight-commander.org/ticket/3682 + +For everyone who currently uses app-misc/mc[-xdg], or has not started +mc for so long that it hasn't had a chance to migrate its configuration, +upgrading to 4.8.27 or newer will result in Midnight Commander +effectively reverting to default user configuration. In order to prevent +this from happening, make sure automatic migration is available: + + echo 'app-misc/mc xdg' >> /etc/portage/package.use + emerge --oneshot