debian-junior-live-system) or should the live CD included into
the blend package itself (e.g. debian-junior)?
There may some pros and cons for both options. I may prefer the
option of a dedicated package + provide a guideline and naming
convention in the blends documentation + some meta information
about the Live Systems in the blend project (part of the blend
framework).
* The developer follows the blends guideline
* The build system look into the blends projects
* Checkout the live systems defined in the project
* Build and deliver the artifacts
* The package itself is just the description / configuration of
the artifact, but not the artifact itself.
Why? We can manage those packages independently. The blend
package will hopefully be part of the Debian installer. The Live
Systems may just an additional artefact of the project. Let's
say, we build a live CD to try Debian Junior on a desktop and
build an image for Debian Junior on a mobile device. Those
projects can be in different states (from experimental to
stable). A bug may affects System X but not Y. The build system
itself may different.
If I didn't miss something, we are more flexible to manage
packages, when they are independent.
Would be nice to know if somebody has concerns about it.
Have blends on cdimage.debian.org would be a big benefit for the
Debian project. I'm not sure whether all images *must* be build
on the same way/tools. At least across the blends projects we
should try to have the same way.