2011/2/13 Koen Kooi <[email protected]>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > The new TSC is holding a meeting next week and we wanted to see if > anyone wants to suggest items we put in the agenda for the meeting. > > If you have such items, please let us know by replying to this mail. >
- come to a set of minimal quality requirements for our recipes/packages (e.g. must fetch, minimal required headers etc). My proposal would be to use the yocto requirements as a starter - splitting our metadata into multiple layers I can think of the following: - oe core layer (shared with yocto - oe layer (or oe extra's or whatever you want to call it; containing recipes that are generic, not in oe-core and considered to be of common use) - maybe oe-old or so layer (recipes that are not maintained any more) - layer per distro for distro specific stuff - layer per machine (or maybe soc family, I can imagine it makes sense to keep BB and BB-XM together; similarly for the kirkwoord variants) - vendor specific layers (if needed), e.g. ti (although maybe that stuff could also go into a machine layer) Rationale is that users can pull in only those layers that they need. - consider a version based release mechanism yocto has a release model, intermediate versions are aiming to build but are considered to be less mature. If our core recipes follow this model, I can imagine it is a good strategy to follow in oe too. Frans _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
