Hi, On 02/10/12 17:43, Jerrod Peach wrote: > I'm also starting to think there might be a better way to handle this with > Yocto's concept of distros (perhaps have a distro for printer X, and a > different one for printer Y, each pointing at versions of code that are > good for the respective printer), but my research so far hasn't given me > enough information on distros to know if this is a reasonable approach. > (I've poked through some of the documentation and the mailing list > archives.) So, what do you all do for releasing code? Does anyone have a > situation similar to mine? (I can't imagine I'm unique, but maybe I'm more > special than I thought.) Even if you don't have a situation like mine, > what would you suggest I do for releasing code for our printers?
Sounds to me like your situation implies a single distro + multiple machines, one for each distinct printer model; you can then specify revisions on per-machine basis. Whether you specify the machine specific revisions in the bb files, or whether you pull it together into an include file is a matter of taste more than anything else I suspect, as long as everyone knows what the deal is. But I'd advise not to specify package revisions local.conf, that's really for the developer/user to tweak, and it should not be stored in vcs, doings so just causes pain. I use the unified include file in Guacamayo for the packages that we maintain; this is for convenience, as during the development cycle I use AUTOREV for these packages, but for an actual release specify the revisions explicitly and having them all in one place makes this easier to do and not forget anything. See, https://github.com/Guacamayo/meta-guacamayo/tree/master/meta-guacamayo/conf/ for how we got it set up. Tomas _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
