Multi-laptop naming scheme for build files

[James Cameron]

On Wed, Mar 14, 2012 at 10:24:07PM +0000, Alan Jhonn Aguiar Schwyn wrote:
> > 1. single-character ID for product type. 'a' for XO-1, 'b' for XO-1.5,
> > 'c' for XO-1.75, ...
> > 2. build number
> > 3. a "."
> > 4. extension
> >
> > e.g.
> >
> > 'a900.img' - build 900 copy-nand image for XO-1
> > 'b900.zd4' - build 900 4GB image for XO-1.5
> > 'c900.zd4' - build 900 4GB image for XO-1.75
> >
> > Thoughts/other ideas?
> >
> 
> It's a good idea.. simple to remember easy (a, b, c...)
> 
> Why use the build number? Not is better use the version of Sugar?
> 
> Ex: os883 is Sugar 0.94.1
> and you need remember that 883 is 0.94...
> 
> Only a idea...

The build number meaning has become overloaded.  I dislike having it
exposed.

The .au deployment installation method avoids some of this by
providing a user interface for installation of builds.  I was not
involved in the design.  They unzip a file onto a USB drive, which
contains an OpenFirmware script and the build images.

But the design does mean that file names are a non-issue for deployment.

We already use 0, 1 and 2 to mean XO-1, XO-1.5, and XO-1.75, so adding
another set of letters seems a duplication.

-- 
James Cameron
http://quozl.linux.org.au/