Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Features in Yocto Project 1.7
Date: Tue, 25 Mar 2014 10:16:21 -0500	[thread overview]
Message-ID: <53319DC5.8050503@windriver.com> (raw)
In-Reply-To: <5331935A.6060009@enea.com>

On 3/25/14, 9:31 AM, 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.

I agree.. generating images, SDKs or other consumables from package feeds is 
high on my wish list as well.

I think we've finally gotten to the point where WIC, rootfs generation and other 
pieces are in place to help do an implementation of this.

--Mark

> 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
>>
>>
>>
>



  reply	other threads:[~2014-03-25 15:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24 16:00 Features in Yocto Project 1.7 Richard Purdie
     [not found] ` <533058C1.3000102@arm.com>
2014-03-24 16:18   ` [yocto] " Richard Purdie
2014-03-24 19:40 ` Rifenbark, Scott M
2014-03-25  0:11 ` --conf Was: " Trevor Woerner
2014-03-25  5:50   ` Martin Jansa
2014-03-26 14:33     ` Trevor Woerner
2014-03-26 14:38       ` Otavio Salvador
2014-03-26 20:45         ` Nicolas Dechesne
2014-03-27 16:33           ` Trevor Woerner
2014-03-26 14:46       ` Martin Jansa
2014-03-25 12:22 ` Otavio Salvador
2014-03-25 15:14   ` Mark Hatle
2014-03-25 14:31 ` David Nyström
2014-03-25 15:16   ` Mark Hatle [this message]
2014-03-25 17:37   ` [yocto] " Philip Balister
2014-03-27 10:47   ` David Nyström
2014-03-28 15:23     ` Otavio Salvador
2014-03-28 18:00       ` David Nystrom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53319DC5.8050503@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox