Replies: 2 comments 2 replies
-
Clearly nobody felt like fixing it and the license for brew says that it is provided "AS IS", so nobody needs a really good reason. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
And the matching PR for 'glibc.rb' as suggest by MikeMcQuaid is Homebrew/homebrew-core#276609 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Additional Info
Output of
brew configOutput of
brew doctorDescription of issue
A couple of days ago, there was a glibc update in Homebrew, with the result that my locale data got lost (again!), and I was getting locale warnings from various homebrew components, like perl, for example:
Whilst this is easily fixed via
/home/linuxbrew/.linuxbrew/Cellar/glibc/2.39/bin/localedef -i en_NZ -f UTF-8 en_NZ.UTF-8, I notice that the glibc.rb formula itself actually supports doing this automatically in the post_install, via this code:However, this doesn't actually work, as the 'brew' wrapper filters the current environment before this postinstall gets to run, and LANG (and LC_*) are stripped out of the environment as part of this.
There are open issues dating back to 2022 which note this behaviour - so is there a really good reason why this hasn't been fixed yet?
All that's required would be to add "LANG" to the list of variables that are included in the filter....
Beta Was this translation helpful? Give feedback.
All reactions