Tiny Core Base > Alpha Releases

Tiny Core 10.0 Alpha 2 Testing

<< < (4/6) > >>

Juanito:
Could you propose a patch?

andyj:
Here's a patch. This is the behavior I don't understand:


--- Code: ---tc@box:~$ localedef --list
en_US.utf8
tc@box:~$ locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
tc@box:~$ locale -a
C
en_US.utf8
POSIX
tc@box:~$

--- End code ---

Why are all the LC_* variables set but not LC_ALL and where does this happen?

Regarding php/pspell, thanks for the update. Unfortunately it didn't fix the futex hang in the pspell_check function. I tried changing gcc optimization to -O2 instead of -Os, but that didn't help.

Juanito:
I recall reading somewhere that $LC_ALL (and $LANGUAGE) being unset was the default behavior in order to allow the other $LC_* settings to be overridden without having to change them all?

andyj:
That seems reasonable and I don't doubt it based on what I was able to find. As far as I know perl is the only thing complaining, and I'm only using perl because some of the "make test" are written in perl and the language setting doesn't seem to affect the test outcomes. I personally have no desire to use perl, so if you choose not to accept the patch I'm fine with that. The multiple language variables does seem to be the result of cruft from a lot of packages and lack of early standardization. But, a line exporting LC_ALL in /etc/profile when it's not being set anywhere seems like cruft too. It seems like if we're going to export it then we should set it, or if we're not going to set it then don't export it.

Juanito:
I did a bit of checking and found this in the debian wiki locale section:
--- Quote ---Warning - Using LC_ALL is strongly discouraged as it overrides everything. Please use it only when testing and never set it in a startup file
--- End quote ---

..anyway, it's good your question prompted some thought on the subject.

Navigation

[0] Message Index

[#] Next page

[*] Previous page