Source bucket for LEB

Registered by Bernie Ogden

Provide source and build scripts for all binaries comprising LEB images. Alongside the downloadable images at http://releases.linaro.org/12.02/ubuntu/ there would be a directory containing debian packages that can be built with suitable dpkg invocations. This would permit LEB consumers to easily rebuild any binary in the LEB for purposes of experimentation, debug or provenancing.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
Accepted for trunk
Implementation:
Unknown
Milestone target:
None
Completed by
Ricardo Salveti

Related branches

Sprints

Whiteboard

[rsalveti, Oct 9, 2012] This is now covered by the source/repository publishing that happens on every release, such as http://releases.linaro.org/12.09/ubuntu/repository. From next release on we'll also be setting a static repository, that will contain all the packages and sources used between our releases (not only the tarballs).

This probably falls within the remit of blueprint linaro-platforms-q112-maximizing-usefulness-leb

Top-level requirements:
1) Getting the source for every binary in the LEB must be practical - i.e. it must be possible to get some package without hunting through N source repositories.
2) It must be possible to rebuild the binary from the source - i.e. all configuration utilities must be included, configuration/build invocations must be recorded. Supplying buildable Debian source packages is sufficient to meet this requirement.

Note that there is no requirement for cross-compilation.

Use cases include:
1) Bundling LEB into third-party products. It is easier to meet open license obligations if it is easy for the third party to rebuild the LEB from source.
2) Experimentation. Linaro customers can install an LEB onto one of the supported platforms, then easily hack it to understand how it works.
3) Demonstration platform. The LEB can be used as a demonstration platform for development tools. This is easier if sources (and debug symbols) are easily obtained following simple instructions.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.