|
From: Hans-Bernhard B. <HBB...@t-...> - 2014-11-16 22:00:45
|
Am 16.11.2014 um 18:20 schrieb Daniel J Sebald: > On 11/15/2014 05:02 AM, Hans-Bernhard Bröker wrote: > >> As an aside, I propose to upgrade the entire auto-tools configuration to >> current versions (autoconf 2.69, automake 1.14). Some of our automake >> support scripts are almost a decade out of date... This I will only >> check in after some discussion. > > If it is a minor change. My system is about three years old with a few > minor upgrades and has autoconf 2.66, automake 1.11.1. The only > reluctance would be if any tools require the builder (common user, not > bundle maintainer) to upgrade. It would require people using the CVS source to have the autotools versions mentioned above, or newer. Those are both at least a year old now, so it's not like I would be requiring bleeding-edge versions ;-) > Changelogs will be part of the "changeset", written by whomever > creates the changeset (just follow the defined format). Absolutely not. ChangeLog has to be maintained anyway. > It's much > easier to browse through changes in git and hg, create changeset, etc. For those working off work-in-progress sources, sure. But what about people using an actual release version? > * True hidden surface code. (I've had in mind for a while to generalize > the hidden line segment code to hidden triangle surfaces.) That wouldn't be a generalization. It'd be a complete re-implementation that has essentially no relation to the existing code. > * Better integration with other programs using emerging trends (say SQL > or something). Wow, ROTFL. That must be the first time in well over 20 years that anyone has called SQL, of all things, an "emerging trend". ;-) |