https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246618
--- Comment #11 from Tijl Coosemans <t...@freebsd.org> ---
(In reply to Tijl Coosemans from comment #10)
> 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?
Apparently one can package a /home like that using tar cf home.tar --option
hdrcharset=BINARY /home. Without that option tar converts all file names from
the current locale to UTF-8.
If "EXTRACT_CMD=${SETENV} LC_ALL=en_US.UTF-8 ${TAR}" in the port Makefile works
I would use that for now. If more ports require this we can do something in
bsd.port.mk. When FreeBSD 11 goes EOL we can also use C.UTF-8 as the ports
tree locale.
Dynamically linked tar may not error but it will try to convert the UTF-8
characters to US-ASCII and replace any character that fails with a question
mark so whatever fix you choose you shouldn't condition it on QEMU_EMULATING.
--
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"
