Re: Gripe: working on configure now requires Automake installed locally

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL Development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Gripe: working on configure now requires Automake installed locally
Date: 2000-06-12 14:50:46
Message-ID: 622.960821446@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Tom Lane writes:
>> You seem to be relying on automake's aclocal program to combine the
>> config/*.m4 files into aclocal.m4. I can see no value in introducing
>> this additional package dependency, since as far as I can tell aclocal
>> isn't doing anything for us that 'cat' couldn't do.

> We need it if we ever want to use libtool unless you want to include half
> of libtool into CVS.

Huh? libtool doesn't require automake; I've been using it quite
successfully for libjpeg without any automake.

My impression so far of automake is that it imposes a ton of mechanism
and unpleasant restrictions (like, say, not being able to make INSTALL
an absolute path, as any half-sane person would do) in return for darn
little usefulness. I'm going to want to be convinced that it's a good
idea for Postgres...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-06-12 15:01:01 Re: ALTER TABLE DROP COLUMN
Previous Message Zeugswetter Andreas 2000-06-12 14:46:51 Re: FORMAL VOTE ON =- and similar