On Thu, 2013-05-02 at 11:36 +0100, Paul Eggleton wrote: > On Thursday 02 May 2013 11:16:30 Phil Blundell wrote: > > On Wed, 2013-02-06 at 14:25 +0100, Martin Jansa wrote: > > > * check also RSUGGESTS, RCONFLICTS, RPROVIDES, RREPLACES > > > > These are already checked by recipe_sanity.bbclass. There's probably no > > need to check them again here. > > recipe_sanity.bbclass doesn't get used by default - I guess you are enabling > it explicitly?
Yeah, or rather, it's used by default in meta-micro. > I wonder if we should either (a) move all the recipe checks to > recipe_sanity.bbclass and enable it by default, or (b) move any currently > there and not covered by insane.bbclass to insane.bbclass and delete > recipe_sanity.bbclass. Either of those sounds reasonable enough to me. I think the original concept was that recipe_sanity was for errors that you could identify statically at recipe parse time, and insane.bbclass was for checks against the output artifacts (that you could only do after compiling and packaging) but that line does seem to have gotten a bit blurred over time. p. _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
