On Mon, Jan 9, 2017 at 2:25 AM, Patrick Ohly <patrick.o...@intel.com> wrote:
> > > > > In principle I agree. Okay, let's separate the two. > > I hit one snag when starting to do that: the implementation of download > removal depends on do_rm_work from rm_work.bbclass for hooking into the > build of a recipe at the right place. > > I can't think of an easy way of avoiding that without duplicating the > complex logic from rm_work.bbclass, which itself is currently about to > change, so I'd prefer to keep rm_work_and_downloads.bbclass as proposed. > Sounds good to me. If it turns out someone would like them separate in the future, we can schedule the time to do it then.
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
