[oe] [PATCH] beagleboard-olddemo-image: saved off beagleboard-demo-image

[Jason Kridner]

On Tue, Aug 17, 2010 at 3:54 PM, Frans Meulenbroeks
<fransmeulenbroeks at gmail.com> wrote:
> 2010/8/17 Jason Kridner <jkridner at beagleboard.org>:
>> I want to use the name beagleboard-demo-image for what actually ships
>> with the xM boards.
>>
>> Signed-off-by: Jason Kridner <jkridner at beagleboard.org>
>> ---
>>  recipes/images/beagleboard-olddemo-image.bb |   30 +++++++++++++++++++++++++++
>>  1 files changed, 30 insertions(+), 0 deletions(-)
>>  create mode 100644 recipes/images/beagleboard-olddemo-image.bb
>>
>> diff --git a/recipes/images/beagleboard-olddemo-image.bb b/recipes/images/beagleboard-olddemo-image.bb
>> new file mode 100644
>> index 0000000..d83281c
>> --- /dev/null
>> +++ b/recipes/images/beagleboard-olddemo-image.bb
>> @@ -0,0 +1,30 @@
>> +# Demo image for beagleboard
>> +
>> +IMAGE_LINGUAS = "de-de fr-fr en-gb en-us pt-br es-es kn-in ml-in ta-in"
>> +
>> +XSERVER ?= "xserver-xorg \
>> +           xf86-input-evdev \
>> +           xf86-input-mouse \
>> +           xf86-video-fbdev \
>> +           xf86-input-keyboard \
>> +"
>> +
>> +ANGSTROM_EXTRA_INSTALL ?= ""
>> +SPLASH = "exquisite exquisite-themes exquisite-theme-angstrom"
>> +
>> +export IMAGE_BASENAME = "Beagleboard-demo-image"
>> +
>> +DEPENDS = "task-base"
>> +IMAGE_INSTALL = "\
>> +    ${XSERVER} \
>> +    ${ANGSTROM_EXTRA_INSTALL} \
>> +    task-beagleboard-demo \
>> +    ${SPLASH} \
>> +    "
>> +
>> +IMAGE_PREPROCESS_COMMAND = "create_etc_timestamp"
>> +
>> +#zap root password for release images
>> +ROOTFS_POSTPROCESS_COMMAND += 'install_linguas; ${@base_conditional("DISTRO_TYPE", "release", "zap_root_password; ", "",d)}'
>> +
>> +inherit image
>> --
>
> What about a better name? E.g. XM-demo-iimage?

I don't know why we need two demo images.  This should run on Rev Cx as well.

>
> And to widen the question: do we want to maintain customer/supplier
> specific images in the oe repo?
> The company I work for also has some images, but for now we opted to
> keep them in a private overlay.

I want this to be public and part of the mainline to make it easy for
people to reproduce.  It is for a relatively broad target.  Is there a
reason it shouldn't be there?

>
> Frans
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>