[yocto] [OE-core] Features in Yocto Project 1.7

[David Nystrom]

On 28 Mar 2014 16:24, "Otavio Salvador" <otavio at ossystems.com.br> wrote:
>
> Hello David,
>
> On Thu, Mar 27, 2014 at 7:47 AM, David Nyström <david.nystrom at enea.com>
wrote:
> > On 2014-03-25 15:31, David Nyström wrote:
> >>
> >> On 2014-03-24 17:00, Richard Purdie wrote:
> >>>
> >>> As development on 1.6 finishes up, its time to think about what we
> >>> should be doing in the 1.7 cycle.
> >>>
> >>> I think from my perspective, in 1.7 I'd like to see us looking at
> >>> "Developer Workflow". Its a generic topic which I think covered
multiple
> >>> areas (in no particular order):
> >>>
> >>> * the ADT/SDK and how it intergrates into the rest of the system
> >>
> >>
> >>> * toaster
> >>> * python devshell
> >>> * exteralsrc.bbclass
> >>> * memory resident bitbake
> >>> * how a standalone app developer might build an image
> >>
> >>
> >> +1
> >> My wishlist:
> >>
> >> 1. Assembly of an image from a package repository using the SDK.
> >> 2. Ability to easily package multiple kernel flavours(builds with
> >> different kernel configs) with linux related bbclass:es.
> >
> >
> > 3. layer based repository splitting.
> > --
> > When having multiple users of a base repository. Ease management of
> > customized repos, by having he ability to mark layers as "split layers",
> > this would yield a separate repo per "split layer", which would contain
> > packages modified/created by this layer.
>
> So you mean:
>
>  * base package feed
>  * meta-qt5 package feed
>
> and in case meta-qt5 adds a bbappend, in a existing recipe, what will
> be the behavior?

If bbappending the bash recipe, f.ex.
bash packages will be generated without meta-qt5 mods in base repo, and
subsequently generated with qt5 mods in the meta-qt5 repo.

//DD

>
> > Said packages would also be built for the base repo, but without
split-layer
> > modifications.
> >
> > A customized distro would use a compound of the base repo + split repo,
> > where the split repo would have higher priority.
> >
> > I guess this could mean one deploy directory per split-layer.
>
> This part is easy as all package managers we use has support for it (I
> think) so it is a matter of proper generating those and add a method
> to include it in the image, the first part is the most complicated one
> I think...
>
> --
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20140328/bce4224e/attachment.html>