Some long term oe improvements I'd like to see, but which are unlikely to be able to go into oe-core as it stands today (largely for compatibility reasons, though some would also just be controversial). I'm not 100% confident that these are all ideal, but all are things I'd like to consider.

oe-core-invasive.taskpaper

- Break up base.bbclass and bitbake.conf into a sane structure
- Drop make handling from base.bbclass in favor of an explicit bbclass
- Remove nearly all globally exported shell variables in favor of explicit task level exports
	https://gist.github.com/kergoth/8410245
- More declarative, less imperative
	This should help reduce confusion, as well as make it easier to transition file formats
	- Avoid all addtask usage and similar bitbake behavior manipulation from recipes,
	  in favor of providing more hooks
	- Move to consistent inherit locations, e.g. move all to the tops of the recipes,
	  and adjust the bbclasses to support this mode of operation
- Replace do_fetch with a version that calls out to a standalone fetch tool
- Avoid unnecessary .inc usage, so the user doesn't have to chase the metadata around
- Replace our toolchain bits in favor of offloading to crosstool-ng
- Pare down the core, move some of the extraneous bbclasses elsewhere
- Ideally, though it could be extraordinarily painful: drop the full sysroot ${prefix}
  for native/cross in favor of fixing things to actually be relocatable
- Build in support for non-cross operation, if possible. It would of course need something
  along the lines of external-sourcery-toolchain to extract the libc from the host sysroot