From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx-3.enea.com (sestofw01.enea.se [192.36.1.252]) by mail.openembedded.org (Postfix) with SMTP id D6CF26F86A for ; Thu, 27 Mar 2014 10:47:10 +0000 (UTC) Received: from [172.16.141.133] (172.16.141.133) by smtp.enea.com (172.21.1.208) with Microsoft SMTP Server id 14.3.158.1; Thu, 27 Mar 2014 11:47:07 +0100 Message-ID: <533401A8.60304@enea.com> Date: Thu, 27 Mar 2014 11:47:04 +0100 From: =?ISO-8859-1?Q?David_Nystr=F6m?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: =?ISO-8859-1?Q?David_Nystr=F6m?= , Richard Purdie , openembedded-core , yocto References: <1395676843.24890.7.camel@ted> <5331935A.6060009@enea.com> In-Reply-To: <5331935A.6060009@enea.com> X-Originating-IP: [172.16.141.133] Subject: Re: Features in Yocto Project 1.7 X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Mar 2014 10:47:14 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable On 2014-03-25 15:31, David Nystr=F6m 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=20 customized repos, by having he ability to mark layers as "split layers",=20 this would yield a separate repo per "split layer", which would contain=20 packages modified/created by this layer. Said packages would also be built for the base repo, but without=20 split-layer modifications. A customized distro would use a compound of the base repo + split repo,=20 where the split repo would have higher priority. I guess this could mean one deploy directory per split-layer. Br, David > Br, > David > > >> * locked sstate >> >> and probably more I'm forgetting. >> >> If anyone does have things they plan to work on, or ideas for things >> that should be worked on, please do file enhancement requests in the >> bugzilla: >> >> https://bugzilla.yoctoproject.org/ >> >> Cheers, >> >> Richard >> >> >> >