<p dir="ltr"><br>
On 28 Mar 2014 16:24, "Otavio Salvador" <<a href="mailto:otavio@ossystems.com.br">otavio@ossystems.com.br</a>> wrote:<br>
><br>
> Hello David,<br>
><br>
> On Thu, Mar 27, 2014 at 7:47 AM, David Nyström <<a href="mailto:david.nystrom@enea.com">david.nystrom@enea.com</a>> wrote:<br>
> > On 2014-03-25 15:31, David Nyström wrote:<br>
> >><br>
> >> On 2014-03-24 17:00, Richard Purdie wrote:<br>
> >>><br>
> >>> As development on 1.6 finishes up, its time to think about what we<br>
> >>> should be doing in the 1.7 cycle.<br>
> >>><br>
> >>> I think from my perspective, in 1.7 I'd like to see us looking at<br>
> >>> "Developer Workflow". Its a generic topic which I think covered multiple<br>
> >>> areas (in no particular order):<br>
> >>><br>
> >>> * the ADT/SDK and how it intergrates into the rest of the system<br>
> >><br>
> >><br>
> >>> * toaster<br>
> >>> * python devshell<br>
> >>> * exteralsrc.bbclass<br>
> >>> * memory resident bitbake<br>
> >>> * how a standalone app developer might build an image<br>
> >><br>
> >><br>
> >> +1<br>
> >> My wishlist:<br>
> >><br>
> >> 1. Assembly of an image from a package repository using the SDK.<br>
> >> 2. Ability to easily package multiple kernel flavours(builds with<br>
> >> different kernel configs) with linux related bbclass:es.<br>
> ><br>
> ><br>
> > 3. layer based repository splitting.<br>
> > --<br>
> > When having multiple users of a base repository. Ease management of<br>
> > customized repos, by having he ability to mark layers as "split layers",<br>
> > this would yield a separate repo per "split layer", which would contain<br>
> > packages modified/created by this layer.<br>
><br>
> So you mean:<br>
><br>
> * base package feed<br>
> * meta-qt5 package feed<br>
><br>
> and in case meta-qt5 adds a bbappend, in a existing recipe, what will<br>
> be the behavior?</p>
<p dir="ltr">If bbappending the bash recipe, f.ex.<br>
bash packages will be generated without meta-qt5 mods in base repo, and subsequently generated with qt5 mods in the meta-qt5 repo.</p>
<p dir="ltr">//DD</p>
<p dir="ltr">><br>
> > Said packages would also be built for the base repo, but without split-layer<br>
> > modifications.<br>
> ><br>
> > A customized distro would use a compound of the base repo + split repo,<br>
> > where the split repo would have higher priority.<br>
> ><br>
> > I guess this could mean one deploy directory per split-layer.<br>
><br>
> This part is easy as all package managers we use has support for it (I<br>
> think) so it is a matter of proper generating those and add a method<br>
> to include it in the image, the first part is the most complicated one<br>
> I think...<br>
><br>
> --<br>
> Otavio Salvador O.S. Systems<br>
> <a href="http://www.ossystems.com.br">http://www.ossystems.com.br</a> <a href="http://code.ossystems.com.br">http://code.ossystems.com.br</a><br>
> Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750<br>
> --<br>
> _______________________________________________<br>
> Openembedded-core mailing list<br>
> <a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.openembedded.org</a><br>
> <a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
</p>