Excerpts from David E. Wheeler's message of Thu Jan 07 19:43:25 -0500 2010:
Yes, if there wasn't already significant investment in `make` for PostgreSQL,
I'd be looking into something else.
Yes, if there wasn't already significant investment in `make` for PostgreSQL,
I'd be looking into something else.
something else, or write a new installer, or whatever.
I was suggesting that you have a level of indirection between the PGAN client
and make so that it's easy to support both the current standard installer
(make) and whatever else might come in the future.
If your client always runs
make
make install
make installcheck
then you are *stuck* using make and good luck shoehorning anything else in
there.
If your client looks for
./build
./install
./installcheck
# or whatever, don't be fussed about the names
then you can use make now and trivially use, you know, Korn shell or whatever
when the postgres community goes nuts and switches en masse.
And yes, I have extended a Makefile, for
[pgTAP](http://github.com/theory/pgtap/blob/master/Makefile). It was painful
for someone who knows nothing about `make`, but it works well enough.
Writing make is pretty easy. Writing something that writes make and shell and[pgTAP](http://github.com/theory/pgtap/blob/master/Makefile). It was painful
for someone who knows nothing about `make`, but it works well enough.
whatever else is less so; that's what I was referring to.
hdp.
