As a developer that lives on “master”, I find it hard to remember the context of older releases. That is human nature. When faced with an older product that was only supported in daisy or fido

So it's great that this is happening, but unfortunately I'm not going to be able to make it to this one, and I suspect there will be many others who would like to participate but can't be present in

Richard Purdie <richard.purdie@...> wrote: This sounds like a really good idea to me. There's definitely some duplication of effort here. Users currently need to choose between

As we do around each Embedded Linux Conference, OpenEmbedded will host a developer meeting to discuss the state of OpenEmbedded and what efforts we should focus on over the next six months or so. All

Our current stable release policy is to maintain the stable release branches for around a year. Maintain means merging patches, running the branch through the autobuilder periodically and running the

I've created a wiki page: http://www.openembedded.org/wiki/FOSDEM_2017 to help get things organized. If you need an account sign up and ping me to approve it. Philip

I could bring along 1. Raspi2 + Hifiberry + Speakers + Midi-Keyboard + Xbox-controller 2. a SDCard full of desktops/multimedia/office/games using 1. 3. 2 days time 4. ?? - let me know Andreas

Every year since 2007, OpenEmbedded has a stand at FOSDEM (http://www.fosdem.org) From the first year: https://www.flickr.com/photos/32615155@N00/405229708/in/album-72157594561002629/ Belen and I

No objection to getting rid of them, but I would love to see them replace with one or more sample WIC configurations that resulted in -exactly- the same behavior. --Mark

Folks, For years we have wanted to get rid of the hddimg/iso type, we now have the WIC tool integrated into OE-Core such that we can build properly partitioned disk images. Historically the hddimg

I think we might be talking cross purposes. If you just need the dependencies of a specific piece of software, your existing class will probably work as it does today. The difference is that you will

<schnitzeltony@...> wrote: Partial answer: This won't work for plugins... Andreas

<richard.purdie@...> wrote: Yes - I did not expect Sounds a bit more insane to what I am doing currently... The more I think of this, I start hoping that recipe specific sysroot plus

Kind of. Otavio also proposed we could use the checksum data to decide if a given sysroot matched and then have a pool of sysroots and make it all task specific. Right now, I think this would

Basically, no, there won't, at least not out the box. It would likely be straightforward to have the code populate a sysroot which corresponded to the image, or "sum" all the individual

Thanks!

Well, I'm sure you could have figured it out but: http://git.openembedded.org/openembedded-core-contrib/log/?h=rpurdie/wip-rss and you need bitbake master-next. Cheers, Richard

After some time working in the Open-embedded project, i noticed that we don't have a unified manner to create tests for different components in the project. Currently we have duplicated test code

So, ehm, do you have something non-poky users can test? regards, Koen

OpenEmbedded will have 2 tables at FOSDEM. 2! If you can help to fill them up by bringing something to demo, get in touch with Philip Balister. Cheers Belén ---------- Forwarded message