On Mon, Aug 02, 2004 at 12:40:34AM -0400, Colin Walters wrote: > A package should *always* call a specific version of automake. If a > package directly invokes "automake", that's a bug. It should instead > call automake-1.8, automake-1.4, whatever is known to work. Most don't bother. Nor can you really blame the package authors since most of them wrote their configuration stuff without realising a bunch of nutters would start issuing a zillion differently incompatible autoconf tool sets with more new syntax bugs than perl > The automake binaries are versioned for a reason - so installing a new > version doesn't break builds. Patches to move to a new version should > be upstream, since they are more likely to be familiar with their build > system and the effects of new automake versions on their packages. So you want to end up in the state where CD #2 is "autoconfs" 8) ?
