With the variety of platforms Trinity targets, I am concerned that providing static configure and make files will be more trouble than it is worth. You can get very strange errors if the automake files on the system are even a slightly different version than those that generated the static files (trust me, been there done that!). Now consider that Trinity officially supports Debian Lenny through Ubuntu Maverick (at this point) and I think you have a recipe for disaster.
I'll probably copy the instructions off the Wiki and place them in a text file called BUILDING or similar.
Thoughts? Comments?
I'm no expert. I trust your expertise. Currently my concern is ensuring my build scripts support both svn and tarballs.
I will test with the presumption that the make and configure files will be built locally on-the-fly.
I agree that building the make and configure files locally sounds safer. :)