setup.py inconsistencies and dependency issue about dt-schema HOT 2 CLOSED

Thanks for the review. My first python project...

On my system (ubuntu), pip as root installs to /usr, but without root goes in the user's home dir.

While I'm happy to make packaging easier, there's a couple things you should be aware of. The only thing really tested for sure is current master of dt-schema with current Linus master and linux-next. I barely keep up with that. The expectation is users stay up to date with dt-schema. Current users are developers tracking current kernels anyways. Older kernels with current dt-schema will for sure have failures because the meta-schema checks get better (mostly implementing common mistakes in reviews as meta-schema) and I fix the existing schema for those new checks as we go. I generally keep any meta-schema changes that require kernel fixes in my local tree for a bit before publishing. Current kernels with older dt-schema will usually work, but then we miss the meta-schema improvements. There's a variety of ways to solve these issues when necessary. I just hope to put that off, and don't want distro packaging to be the reason.

from dt-schema.

@afaerber PR #28 fixes this.

FYI, I'm going to switch to date based versions. YYYY.MM

from dt-schema.