[reSIProcate] Build systems.

[Alan Hawrylyshen]

All;

I just want to chime back in on this thread and point something out  
that I have overlooked or not stressed this time around:

We are NOT considering abandoning our current build system unless it  
makes sense to do so.

At this point, it makes no sense to do so.

I think we should focus on what the gaps are between where the  
current system is and the items that we need for more formal  
packaging and runtime detection of capability mismatches (or ABI  
mismatches).

Several people have volunteered to assist with getting the  
installation of the library polished and adding some dynamic version  
querying and embedded compatibility numbers in the ELF libraries will  
get us everything that I think we want.

The ABI and stability issues will boil down to developer discipline  
and a set of guidelines for changing the ABI. This is the same no  
matter what build system you use.

In short -- let's get our current system to the point where it is a  
first class build and install mechanism on the architectures we want.

Then we'll branch out and see how to get the other things we might need.

Better to have 20 people who know the build system then be trapped to  
the 'great expert gurus' of auto-splat.

Thanks again,

Alan