https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246618
--- Comment #10 from Tijl Coosemans <t...@freebsd.org> --- (In reply to Jan Beich from comment #8) > Tijl, why bug 215882 limits USE_LOCALE to configure and build phases? This > port needs to set UTF-8 locale during extract phase. The logic behind that was that there's ports tree code and upstream code. That commit forces the C locale for the ports tree. USE_LOCALE can then be used to set a different locale for the upstream code. I agree it would make sense to extract files using the upstream locale, but I find it strange that tar worries about encoding. It should just treat file names as binary data like the file system does. How else can it handle packing and extracting /home with users using different locales? The error with static tar is probably because it cannot load modules from /usr/lib/i18n. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-python@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
