Re: [yocto] [OE-core] RFC: Improving the developer workflow

2014-08-24 Thread Paul Eggleton
Hi Nicolas, Apologies for the delayed reply. On Friday 08 August 2014 10:04:19 Nicolas Dechesne wrote: > On Thu, Aug 7, 2014 at 11:10 AM, Paul Eggleton > wrote: > > Example workflow > > > > > > I won't give a workflow for every possible usage, but just to give a basic > > examp

Re: [yocto] [OE-core] RFC: Improving the developer workflow

2014-08-12 Thread Tim O' Callaghan
Hi, Another approach I would like to suggest is the one that CoreOS has in place, that they call fastpatch. https://coreos.com/using-coreos/updates/ Essentially two root partitions, and boot to switch between the new image while leaving the old one intact as the last known good. It avoids the

Re: [yocto] [OE-core] RFC: Improving the developer workflow

2014-08-08 Thread Mike Looijmans
On 08/07/2014 11:10 AM, Paul Eggleton wrote: ... * Provide tools to allow modifying software for which a recipe already exists. If the user has an external source tree we use that, otherwise we can fetch the source, apply any patches and place the result in an external source tree, possibly mana

Re: [yocto] [OE-core] RFC: Improving the developer workflow

2014-08-08 Thread Nicolas Dechesne
On Thu, Aug 7, 2014 at 11:10 AM, Paul Eggleton wrote: > Example workflow > > > I won't give a workflow for every possible usage, but just to give a basic > example - let's assume you want to build a "new" piece of software for which > you have your own source tree on your machine.