Publish customization keys used to create images with Activities

[mchua]

When an image containing Activities is published, that image contains both an underlying build plus Activities from some customization key. For instance, build 767 + some customization key = our latest G1G1 image.

It would be easy and useful to publish the customization key used to create images with Activities, perhaps in the image folder itself (imagine http://download.laptop.org/xo-1/custom/g1g1/gg-767-4/customization-key.zip).

One could imagine an Activity maintainer wanting to know what version of her Activity was shipped, or a user who wanted to keep their current build but update just the G1G1 activities, or a developer wondering what versions they'd get if they clean-installed.

[mchua]

See http://blog.melchua.com/2008/12/04/what-versions-of-activities-are-shipped-with-g1g1/ for a description of the saga that inspired this ticket.

[mstone]

Is http://download.laptop.org/xo-1/custom/g1g1/gg-767-4/gg-767-4.zip unsatisfactory?

Perhaps what you really want is, as pgf suggested, a README?

[cjb]

Oh, hey, check that out. (mchua had asked me if we published customization keys for releases and I said no.)

[mchua]

Ah, thanks - I didn't recognize that. A README with a URL pointing to a wiki page containing an explanation of the various files would resolve my confusion.

I wrote up some text on the build systems wiki page that could be included or linked to within a README at http://wiki.laptop.org/go/Build_system#Files_produced (sanity fact-checking requested).

[mstone-xmlrpc]

Pushing out to 9.1.0, per edmcnierney's request.

[dsd]

http://wiki.laptop.org/go/Customization_stick#Deprecation_warning