On Tue, Nov 06, 2018 at 02:05:27AM +0100, Kevin Kofler wrote: > Zbigniew Jędrzejewski-Szmek wrote: > > The first step is to replace LC_ALL=en_US.UTF-8 with LC_ALL=C.UTF-8 > > (and similarly for LANG=, LC_CTYPE=, etc.) in all spec files. > > But there are probably many more packages where the setting is hidden in > upstream build scripts. That is possible, but I don't think it'll be that widespread. Gnarly upstream build scripts tend to be old, and not all systems always had en_US.UTF-8, so those script should do some autodetection of the available encodings. Anyway, we'll see. > > This will be backwards and forwards compatible, in the sense that packages > > that use C.UTF-8 should build OK on older and newer Fedoras. > > Older Fedoras only since F22 updates / F24 GA, see: > https://bugzilla.redhat.com/show_bug.cgi?id=902094 > > And what about EL? Neither version of EPEL seems to support C.UTF-8. So if somebody wants to support F30+ and EPEL (or F21-) from the same branch, they should probably add additional BR and use one of the more heavyweight locales. Zbyszek _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
