Сравнение locale-gen-3.9-r2 с locale-gen-3.10
| /usr/portage/sys-apps/locale-gen/locale-gen-3.10.ebuild 2026-01-27 11:18:04.668427293 +0300 | ||
|---|---|---|
| 31 | 31 |
# EPREFIX is readonly. |
| 32 | 32 |
local -x MY_EPREFIX=${EPREFIX}
|
| 33 | 33 | |
| 34 |
eapply "${FILESDIR}/${PV}-suppress-bash-setlocale-warnings.patch"
|
|
| 35 |
eapply "${FILESDIR}/${PV}-avoid-chcon-execution-if-missing.patch"
|
|
| 36 | 34 |
eapply_user |
| 37 | 35 | |
| 38 | 36 |
perl -pi -e '$f //= ($. == 1 && s/^#!\h*\K/$ENV{MY_EPREFIX}/); END { exit !$f }' "${PN}" \
|
| ... | ... | |
| 64 | 62 | |
| 65 | 63 |
pkg_postinst() {
|
| 66 | 64 |
while read -r; do ewarn "${REPLY}"; done <<-'EOF'
|
| 67 |
As of version 3.9, locale-gen(8) only supports locale/charmap pairs that are |
|
| 68 |
officially supported by glibc itself. For most users, there should be no |
|
| 69 |
impact. Nevertheless, if running locale-gen(8) raises errors regarding |
|
| 70 |
unsupported combinations, it will be necessary to modify its config file. |
|
| 71 |
The locale.gen(5) man page explains how to determine which are supported. |
|
| 65 |
As of version 3.10, the locale.gen(5) config file grammar has been |
|
| 66 |
simplified. For instance, "en_US.UTF-8 UTF-8" may instead be written as |
|
| 67 |
"en_US UTF-8", or even "en_US". The grammar remains backward compatible with |
|
| 68 |
version 3.9, so there is no requirement to update the /etc/locale.gen file. |
|
| 72 | 69 |
EOF |
| 73 | 70 |
} |