On Tue, Apr 3, 2012 at 9:08 AM, Ricardo Salveti <ricardo.salv...@linaro.org> wrote:
<snip> > Looking at the problem, here's what I think it'd help to fix the situation: > 1 - Overlay PPA becomes the main repository for basic platform > development, without having any hardware specific package (not even > the kernel): > This PPA would be used by all the images we're producing > (stable/unstable), as all the changes would be just related with the > distribution. Once we get newer components that are not related with > hardware enablement, and not critical enough to break compatibility > across images, we would be integrating them at this repository (e.g. > powertop, glmark2, libpng, libjpeg-turbo, etc). > 2 - We create the Development Overlay PPA, to be the main place > carrying the hardware related pieces, like kernel, drivers and > multimedia: > This would be the main PPA used during our own development, always > containing the latest kernel packages from the Linux Linaro and > Landing Team trees. Here we could also integrate components related > with hardware enablement that are not for prime use yet, but would > help people that are always looking for the latest stuff available. > 3 - Create a set of Stable PPAs for every board we're officially supporting: > Here the goal would be to have a single place where we can push the > enablement related changes that are known to be working. At the > Pandaboard case this PPA would contain the 3.1 based kernel with SGX > and HW video decoding working out of the box. Once a new snapshot > based on the development release is known to work in a satisfactory > way, we would simply just copy them over the Stable PPA for the > respective board. This would also help the cases where we have > packages with hw enablement changes that conflict with other boards. > > So in the end we'd be generating 2 sets of hwpacks per board, one > based on the Development Overlay (latest components, even if not > working properly), and one based on the Stable PPAs, that we know > it'll always have a better enablement. Both would be using the same > rootfs, as all distro related core changes will be part of the Overlay > PPA anyway. > > I believe this can simply things a bit, and would not consume much of > our time as the stable repository would just be a snapshot of a known > to be working development PPA. What would the monthly release be based on? The stable PPA? _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
