Peter Humphrey wrote: > On Friday 24 Jun 2016 09:54:35 Dale wrote: > >> I agree that the news item was confusing. The guide it linked to wasn't >> much better either. In the end, I just fiddled with the setting until I >> found a setting that didn't change what I already have, in other words, >> I got a clean emerge -uvaDN world. My first couple runs wanted to >> remove things and I knew the setting wasn't right yet. After it was all >> done, this is what I ended up with: >> >> LINGUAS="en_US en" >> >> I left the LANG setting as is for the moment. > Didn't you set L10N as well? I read the news item as requiring it. >
As I said, the news item and even the guide the news item pointed to doesn't explain much. When I run into a doc that doesn't give me enough info, or so much that it doesn't make sense, then I resort of trying settings until I get a output that tells me that the setting I tried works. At first, I tried "en" but some packages were going to be rebuilt. Then I tried "en-US" and that caused other packages to want to be rebuilt. Then I put in both and I got what I expected, a clean emerge output that showed it wasn't going to change anything from what I already had. I guess when L10N starts causing packages to build differently, I'll add it . As it is, I'm not real sure what if anything it does that affects me. Dale :-) :-)
