pgsql (configure)

Bruce Momjian - CVS writes:

Date: Wednesday, October 25, 2000 @ 17:55:14
Author: momjian

Update of /home/projects/pgsql/cvsroot/pgsql
from hub.org:/home/projects/pgsql/developers/momjian/pgsql

Modified Files:
configure

----------------------------- Log Message -----------------------------

autoconf

Why?

--
Peter Eisentraut peter_e@gmx.net http://yi.org/peter-e/

Bruce Momjian - CVS writes:

Date: Wednesday, October 25, 2000 @ 17:55:14
Author: momjian

Update of /home/projects/pgsql/cvsroot/pgsql
from hub.org:/home/projects/pgsql/developers/momjian/pgsql

Modified Files:
configure

----------------------------- Log Message -----------------------------

autoconf

Why?

My server login checks to see if cvs update grabs configure, and if it
does, it runs autoconf and commits the change. That is usually the only
reason I log in anymore, so it does it automatically. Seems it isn't
hurting anything.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Bruce Momjian <pgman@candle.pha.pa.us> writes:

My server login checks to see if cvs update grabs configure, and if it
does, it runs autoconf and commits the change.

If cvs update grabs configure, then someone already committed the
change.

Perhaps you meant configure.in. If so, I still doubt that this is
a good idea. If someone else is in process of committing
configure-related changes when you log in, the odds are that you
will screw them up, or at least confuse them mightily. configure
has more than one precursor file these days, so you might well commit
a broken copy.

regards, tom lane

Bruce Momjian <pgman@candle.pha.pa.us> writes:

My server login checks to see if cvs update grabs configure, and if it
does, it runs autoconf and commits the change.

If cvs update grabs configure, then someone already committed the
change.

Yes, I meant configure.in.

Perhaps you meant configure.in. If so, I still doubt that this is
a good idea. If someone else is in process of committing
configure-related changes when you log in, the odds are that you
will screw them up, or at least confuse them mightily. configure
has more than one precursor file these days, so you might well commit
a broken copy.

Oh. Interesting.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026