Re: [OE-core] [PATCH v2 3/3] rm_work.bbclass: clean up sooner

2017-02-13 Thread Patrick Ohly
On Mon, 2017-02-13 at 12:19 +, Mike Crowe wrote: > On Monday 13 February 2017 at 11:54:32 +0100, Patrick Ohly wrote: > > To me it seems like the right solution. Inheriting > > release-source.bbclass could be limited to builds which produce > > releases, for example in your CI setup, then

Re: [OE-core] [PATCH v2 3/3] rm_work.bbclass: clean up sooner

2017-02-13 Thread Mike Crowe
On Monday 13 February 2017 at 11:54:32 +0100, Patrick Ohly wrote: > On Fri, 2017-02-10 at 18:32 +, Mike Crowe wrote: > > On Thursday 09 February 2017 at 17:24:39 +0100, Patrick Ohly wrote: > > > On Wed, 2017-02-08 at 13:48 +, Mike Crowe wrote: > > > > On Wednesday 08 February 2017 at

Re: [OE-core] [PATCH v2 3/3] rm_work.bbclass: clean up sooner

2017-02-13 Thread Patrick Ohly
On Fri, 2017-02-10 at 18:32 +, Mike Crowe wrote: > On Thursday 09 February 2017 at 17:24:39 +0100, Patrick Ohly wrote: > > On Wed, 2017-02-08 at 13:48 +, Mike Crowe wrote: > > > On Wednesday 08 February 2017 at 14:04:42 +0100, Patrick Ohly wrote: > The part I'd missed is the all-important

Re: [OE-core] [PATCH v2 3/3] rm_work.bbclass: clean up sooner

2017-02-10 Thread Mike Crowe
On Thursday 09 February 2017 at 17:24:39 +0100, Patrick Ohly wrote: > On Wed, 2017-02-08 at 13:48 +, Mike Crowe wrote: > > On Wednesday 08 February 2017 at 14:04:42 +0100, Patrick Ohly wrote: > > > On Wed, 2017-02-08 at 11:50 +, Mike Crowe wrote: > > > > On Friday 13 January 2017 at

Re: [OE-core] [PATCH v2 3/3] rm_work.bbclass: clean up sooner

2017-02-09 Thread Patrick Ohly
On Wed, 2017-02-08 at 13:48 +, Mike Crowe wrote: > On Wednesday 08 February 2017 at 14:04:42 +0100, Patrick Ohly wrote: > > On Wed, 2017-02-08 at 11:50 +, Mike Crowe wrote: > > > On Friday 13 January 2017 at 15:52:33 +0100, Patrick Ohly wrote: > > > > The right solution is to inject

Re: [OE-core] [PATCH v2 3/3] rm_work.bbclass: clean up sooner

2017-02-08 Thread Mike Crowe
On Wednesday 08 February 2017 at 14:04:42 +0100, Patrick Ohly wrote: > On Wed, 2017-02-08 at 11:50 +, Mike Crowe wrote: > > On Friday 13 January 2017 at 15:52:33 +0100, Patrick Ohly wrote: > > > The right solution is to inject do_rm_work before do_build and after > > > all tasks of the recipe.

Re: [OE-core] [PATCH v2 3/3] rm_work.bbclass: clean up sooner

2017-02-08 Thread Patrick Ohly
On Wed, 2017-02-08 at 11:50 +, Mike Crowe wrote: > On Friday 13 January 2017 at 15:52:33 +0100, Patrick Ohly wrote: > > Having do_rm_work depend on do_build had one major disadvantage: > > do_build depends on the do_build of other recipes, to ensure that > > runtime dependencies also get

Re: [OE-core] [PATCH v2 3/3] rm_work.bbclass: clean up sooner

2017-02-08 Thread Mike Crowe
On Friday 13 January 2017 at 15:52:33 +0100, Patrick Ohly wrote: > Having do_rm_work depend on do_build had one major disadvantage: > do_build depends on the do_build of other recipes, to ensure that > runtime dependencies also get built. The effect is that when work on a > recipe is complete and

[OE-core] [PATCH v2 3/3] rm_work.bbclass: clean up sooner

2017-01-13 Thread Patrick Ohly
Having do_rm_work depend on do_build had one major disadvantage: do_build depends on the do_build of other recipes, to ensure that runtime dependencies also get built. The effect is that when work on a recipe is complete and it could get cleaned up, do_rm_work still doesn't run because it waits