portupgrade, automake14 -> automake19

[Dan Nelson]

In the last episode (Jun 09), Giorgos Keramidas said:
> On 2005-06-09 11:01, Tony Shadwick <tshadwick at goinet.com> wrote:
> > Could someone give me a quick hint on switching from automake14 to
> > automake19 using the ports tree without wreaking total havock on
> > dependencies? :)
> 
> If you are asking what portupgrade will do with the installed ports,
> then there's nothing to worry about.  Just run portupgrade -a and it
> will take care of building the necessary auto* ports too.
> 
> If you are using automake14 in software you write or build yourself
> outside of the Ports tree, don't.  For an example of what may go
> wrong, see the misc/81558 problem report:

I have never had problems using the numbered auto* ports when building
programs from CVS trees.  Here's the bootstrap script I use: it also
works great on Debian and RedHat, which ship numbered auto* binaries as
well.

#!/bin/sh -e
# Run this to update & generate all the automatic things
#

# Some OSes (RedHat) symlink 'autoconf' to 2.13 even though a perfectly
# good 2.5x is available.  If a numbered version is not found, the
# non-numbered executable will be used, and we hope for the best.
AC=
for i in 259 -2.59 258 -2.58 257 -2.57 256 -2.56 255 -2.55 2.55 254 -2.54 2.54 253 -2.53 2.53 ; do
 if type autoconf$i >/dev/null 2>&1 ; then 
  AC=$i ; echo detected autoconf$AC ; break
 fi
done
AM=
for i in 19 -1.9 18 -1.8 17 -1.7 1.6 -1.6 15 -1.5 ; do
 if type automake$i >/dev/null 2>&1 ; then 
  AM=$i ; echo detected automake$AM ; break
 fi
done

# export these because all 5 need to know the exact name of the other ones
AUTOCONF=autoconf$AC ; export AUTOCONF
AUTOHEADER=autoheader$AC ; export AUTOHEADER
AUTOM4TE=autom4te$AC ; export AUTOM4TE
ACLOCAL=aclocal$AM ; export ACLOCAL
AUTOMAKE=automake$AM ; export AUTOMAKE

rm -rf autom4te*
$ACLOCAL -I .
$AUTOHEADER
$AUTOMAKE --add-missing
$AUTOCONF


-- 
	Dan Nelson
	dnelson at allantgroup.com