olpc-configure

[Jerry Vonau]

I've been using OSBuilder to spin up some custom images, I'm just
wondering if my XO-1.5 is a little strange or if I uncovered a bug.
When olpc-configure is run at first boot and reads the $MFG_DATA in /ofw
the LO tag that is returned has "en_US.UTF8" in it which will never
match: 

if ! locale -a | grep -qx "${SYS_LANG/UTF-8/utf8}"; then 
	    echo "olpc-configure: Locale $SYS_LANG is not supported;"
	    SYS_LANG="en_US.UTF-8"  # better fallback than "C"
	    echo "olpc-configure: Falling back to locale $SYS_LANG"
	fi

Then the default language becomes en_US.UTF-8... So my question becomes 
do I have a funny tag in ofw or is this a bug? If this is a bug, would 
it not be better to source /etc/sysconfig/i18n for a LANG= variable before 
defaulting to the above? Is there some sugar specific reason for the above?
Just want to know what others think. I've patched olpc-configure to work 
around the issue, but the LANG=C in OSBuilder's base routine should go away 
as it's not being used anyway.
 
Jerry

[Bernie Innocenti]

El Sat, 14-08-2010 a las 02:05 -0500, Jerry Vonau escribió:
>  I've been using OSBuilder to spin up some custom images, I'm
> just
>  wondering if my XO-1.5 is a little strange or if I uncovered a bug.
>  When olpc-configure is run at first boot and reads the $MFG_DATA in /ofw
>  the LO tag that is returned has "en_US.UTF8" in it which will never 
The LO tag in your laptop is incorrect.

It should have been "en_US.UTF-8" (with an extra dash). I've already
seen another XO-1.5 like this, but it was a pre-production unit.

Since you get en_US.UTF-8 either way, I would tend not to bother fixing
this bug neither in olpc-configure nor in your mfg-data.

-- 
   // Bernie Innocenti - http://codewiz.org/
 \X/  Sugar Labs       - http://sugarlabs.org/

[Jerry Vonau]

On Sat, 2010-08-14 at 15:15 -0400, Bernie Innocenti wrote:
>  El Sat, 14-08-2010 a las 02:05 -0500, Jerry Vonau escribió:
>  > I've been using OSBuilder to spin up some custom images, I'm just
>  > wondering if my XO-1.5 is a little strange or if I uncovered a bug.
>  > When olpc-configure is run at first boot and reads the $MFG_DATA in /ofw
>  > the LO tag that is returned has "en_US.UTF8" in it which will never
>  
>  The LO tag in your laptop is incorrect.
>  
>  It should have been "en_US.UTF-8" (with an extra dash). I've already
>  seen another XO-1.5 like this, but it was a pre-production unit.
>  
>  Since you get en_US.UTF-8 either way, I would tend not to bother fixing
>  this bug neither in olpc-configure nor in your mfg-data.
>   
I don't want en_US.UTF-8, I want what I set in os-builders'
base/ksmain.10.core.inc file, I'm changing the install language there.
Is there a reason not to do that? Now that you can switch between gnome
and sugar, though that might be a good way to keep the two in sync.

Jerry

[Bernie Innocenti]

Sorry for the long delay, I had overlooked this unreplied message.

El Sat, 14-08-2010 a las 14:35 -0500, Jerry Vonau escribió:
>  On Sat, 2010-08-14 at 15:15 -0400, Bernie Innocenti wrote:
>  > Since you get en_US.UTF-8 either way, I would tend not to bother fixing
>  > this bug neither in olpc-configure nor in your mfg-data.
>  
>  I don't want en_US.UTF-8, I want what I set in os-builders'
>  base/ksmain.10.core.inc file, I'm changing the install language there.
>  Is there a reason not to do that? Now that you can switch between gnome
>  and sugar, though that might be a good way to keep the two in sync. 
The "lang" option in ksmain.10.core.inc gets stored
into /etc/sysconfig/i18n by imgcreate.

Regardless of the contents of the manifacturing data, olpc-configure
will *always* override /etc/sysconfig/i18n on first boot.

To prevent this, you could touch /.olpc-configure from olpc-os-builder.
Take care to also perform the rest of the initialization usually done by
olpc-configure.

-- 
   // Bernie Innocenti - http://codewiz.org/
 \X/  Sugar Labs       - http://sugarlabs.org/

[Daniel Drake]

On 14 August 2010 13:35, Jerry Vonau <jvonau(a)shaw.ca&gt; wrote:
>  I don't want en_US.UTF-8, I want what I set in os-builders'
>  base/ksmain.10.core.inc file, I'm changing the install language there. 
This is basically just an unimplemented feature. We currently assume
that all deployments want to default to the language in the mfg data,
and don't need the opportunity to override that default from software.

If you do want to add a software default which overrides the mfg data,
I expect you'll have to patch the system here and there, you have
discovered one such place.

Daniel