[oe] Improve consistency with bittest content checker + sanitize.py

[Michael 'Mickey' Lauer]

> >> I'd like to point out that the-script-formerly-known-as-sanitize.py checks for *OE* styles
> >>  and *OE* vars, instead of being a generic tool to check bitbake recipes. What I don't
> >> know is where the border between 'bitbake' and 'OE' lies, but bittest is starting to look
> >> like OEtest :)
> >
> >   Let's put bitbake into OE repo then? ;-))
> 
> and reverse http://oe-devel.bkbits.net:8080/openembedded/patch@1.2648.59.105 as well?

No way. Splitting BitBake and OpenEmbedded helped us a lot to draw the
borders between
a generic task executor and cross-building specific issues. We don't
want to go back to the stone ages.

-- 
Regards,

Michael 'Mickey' Lauer | FreeLancer | http://www.Vanille-Media.de