[yocto] Content-tools.

[Stewart, David C]

>From: yocto-bounces at yoctoproject.org [mailto:yocto-
>bounces at yoctoproject.org] On Behalf Of Jeremy Puhlman
>Sent: Monday, June 06, 2011 3:28 PM
>
>As discussed with others when I first dropped the remote-layering patch
>that I was working internally with our management to open our content
>tools, since they would likely be useful as a starting point for yocto
>layering tooling. Due to some personal tragedies I have been a bit
>side-lined, but here they are.

Jeremy - thanks very much to you and to MontaVista for contributing this code to the Yocto Project! 

And also I am very sorry about your personal tragedies. 

>The repository for the tools are here:
>
>git://gitorious.org/content-tools/content-tools.git
>
>The wiki giving a quick run down of everything is here:
>https://gitorious.org/content-tools/pages/Home
>
>The long and the short of it is the tools provide and xml description
>layer for collections/layers, and a method of describing what we call in
>our product solutions. A solution is basically a group of
>collections/layers, configuration options and a like that you would use
>to produce any number of images or what not from a machine
>configuration. You can add multiple solutions together, and they will
>add the collections as needed.
>
>The back end mirroring and content providing components work really
>well, though all the references to collections could be swapped over to
>layers, but it is more or less at that level the name difference is
>largely meaningless. The project creation tool will need some additional
>work. I have added some changes to the tool to make it work with layers
>and sstate a bit better, but I don't think it is completely there, but
>it is more or less a reasonable start. The main thing is the setup.sh
>would need to be taught about the extra stuff in oe-init-build-env and a
>method for dealing with pseudo, which it doesn't at this point.
>
>The work their does kind of hinge on the remote layering code I provided
>before, being in your bitbake to run all the way to the end.  Though,
>integrating what ever fetchers in to the tools is also reasonable, its
>just not where we were doing it.
>
>If you like I can try to post up a example content repository up on our
>ftp server to kick around if you like. The wiki page has a run through
>from beginning to end of the tools and how set an example up.
>
>--
>Jeremy Puhlman
>Montavista Sofware, LLC.
>
>_______________________________________________
>yocto mailing list
>yocto at yoctoproject.org
>https://lists.yoctoproject.org/listinfo/yocto