Open Issues for 7.4

Started by Peter Eisentrautabout 22 years ago4 messages
#1Peter Eisentraut
peter_e@gmx.net

Here are some issues that might need to be addressed before 7.4 goes out:

* ECPG has some new include files such as

datetime.h
decimal.h

that come as part of the Informix compatibility mode. I don't think these
should be installed directly in $includedir because of potential
conflicts. We can't rename them either, without ruining the compatibility
aspect. So I'm looking for suggestions about what to do with them.

* Fix uselessly executable files in the source tree. See my recent post.
Any ideas on that?

* I'm planning to merge some of Jason Tishler's Cygwin README into our
FAQ_MSWIN, plus recently submitted changes for the same file.

* INSTALL, HISTORY and the regress/README need to be regenerated. I'll do
1 and 3 soon, 2 has to wait until the release notes are edited to death.

* There is a bug in configure that prints an ugly error message on systems
without nsgmls and certain weird shells (NetBSD, UnixWare, for example),
because they interpret the construct ${NSGMLS-false} differently.

* I've generated new man pages that are on the ftp server under
pub/dev/doc/man-7.4.tar.gz. They need to be copied into the release
tarball as doc/man.tar.gz. This was a lot of manual work this time, so
any further reference page changes need to be integrated by hand.

* Did we really decide not to rename the check_function_bodies parameter
to something more general? Maybe I've missed it.

* PPC spinlock patch from SuSE.

--
Peter Eisentraut peter_e@gmx.net

#2Marc G. Fournier
scrappy@postgresql.org
In reply to: Peter Eisentraut (#1)
Re: Open Issues for 7.4

On Wed, 5 Nov 2003, Peter Eisentraut wrote:

Here are some issues that might need to be addressed before 7.4 goes out:

* ECPG has some new include files such as

datetime.h
decimal.h

that come as part of the Informix compatibility mode. I don't think these
should be installed directly in $includedir because of potential
conflicts. We can't rename them either, without ruining the compatibility
aspect. So I'm looking for suggestions about what to do with them.

could they not be installed in $includedir/informix? building software
with them should just be a matter of adding -I$includedir/informix, no?

* I've generated new man pages that are on the ftp server under
pub/dev/doc/man-7.4.tar.gz. They need to be copied into the release
tarball as doc/man.tar.gz. This was a lot of manual work this time, so
any further reference page changes need to be integrated by hand.

I changed the build script to rename appropriately, and RC1 should have
the proper files in place ... no?

#3Tom Lane
tgl@sss.pgh.pa.us
In reply to: Peter Eisentraut (#1)
Re: Open Issues for 7.4

Peter Eisentraut <peter_e@gmx.net> writes:

* Fix uselessly executable files in the source tree. See my recent post.
Any ideas on that?

They've been uselessly executable since they were put there. I don't
think this is something that we need to fix in time for 7.4, or even
should risk trying to fix during RC stage.

* There is a bug in configure that prints an ugly error message on systems
without nsgmls and certain weird shells (NetBSD, UnixWare, for example),
because they interpret the construct ${NSGMLS-false} differently.

Okay, should fix that, unless it's harder to fix than it sounds.

* Did we really decide not to rename the check_function_bodies parameter
to something more general? Maybe I've missed it.

There didn't seem to be either widespread interest in this, or good
consensus on what to change it to. I proposed doing nothing here:
http://archives.postgresql.org/pgsql-hackers/2003-10/msg01521.php
and so far as I saw no one responded one way or the other.

* PPC spinlock patch from SuSE.

See my prior response.

regards, tom lane

#4Christopher Kings-Lynne
chriskl@familyhealth.com.au
In reply to: Peter Eisentraut (#1)
Re: Open Issues for 7.4

* Fix uselessly executable files in the source tree. See my recent post.
Any ideas on that?

As far as I'm aware, the only way to fix this is to get into the cvsroot
and chmod them by hand.

Chris