mgetty should use autoconf and automake

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

Sverre Hvammen Johansen wrote:
> > Feel free to send some Autoconf stuff to start with.   
> 
> I am working on implementing autoconf and automake for mgetty.  I am
> almost finished. I will shortly upload a distribution (later this
> day), that can be tried out. I hope that you will accept it. As an
> maintainer you should install autoconf-2.12 and automake-1.3 and GNU
> m4-1.4.
> 
> Some reasons way autoconf and automake should be implemented:
> 
> The goal of Automake is to remove the burden of Makefile
> maintenance from the back of the individual GNU maintainer (and put it
> on the back of the Automake maintainer).

I'm not really sure I'll like Automake (it's nice, but my Makefiles play 
some tricks with CVS, automatic uploading etc. that may be hard to
integrate into a fully-automatized Makefile), but it's not really that
important anyway -- there is not much maintenance happening anyway.

[..]
> Some time in the future there will be support for automatically
> generating packages (eg Debian packages, RPM packages, Solaris
> packages, etc).

My Makefile already has this ("make bindist").

> The configuration scripts produced by Autoconf require no manual user
> intervention when run; which is convenient when configuring large
> source trees.

Well, yes, I know and appreciate this.  It's just the fact that most of
the things "configure" usually checks for are things that aren't really
needed in the mgetty context, while others are impossible to get 100 per
cent right in an automated way.

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert@greenie.muc.de
fax: +49-89-35655025                        gert.doering@physik.tu-muenchen.de