Few notes: - "auto" tools are installer tools and, after all, do good job. Maybe we can download any project that use it, run it once, parse results and put it

Few notes: - "auto" tools are installer tools and, after all, do good job. Maybe we can download any project that use it, run it once, parse results and put it in /etc ? - becouse it's already there. Then next step: build just-detection tools. Side note: just straight 'make all' will detect it too :) And it show additional next problem that auto's already solved - setting up all that inc/lib paths... - m4 should be replaced and not by monstrosity like cmake - GNU's came after MIT's and BSD's, evolved from them. But corporations adapted and assimilated. We need next evolution step: something that forces corporations to spend money on what they use, fund devs or participate in development. OSlicensecertification.orgs should help with that instead of helping corps to be predators becouse some outdated bullshit talks - yea, auto* tools are way overcomplicated - finally do that TTY 2.0 !