distdir:

-rm -rf $(distdir)* $(dummy)

for x in `cd $(top_srcdir) && find . -name CVS -prune -o -print`; do \

for x in `cd $(top_srcdir) && find .\(-name CVS -prune \) -o \( -name .git -prune \) -o -print`; do \

file=`expr X$$x : 'X\./\(.*\)'`; \

if test -d "$(top_srcdir)/$$file" ; then \

mkdir "$(distdir)/$$file" && chmod 777 "$(distdir)/$$file";\

done

$(MAKE) -C $(distdir) distprep

$(MAKE) -C $(distdir) distclean

rm -f $(distdir)/README.CVS

rm -f $(distdir)/README.git

distcheck: $(distdir).tar.gz

-rm -rf $(dummy)

In a release or snapshot tarball of PostgreSQL, documentation files named

INSTALL and HISTORY will appear in this directory. However, these files are

not stored inCVS and so will not be present if you are using aCVS checkout.

If you are usingCVS, you can view the most recent install instructions at:

not stored ingit and so will not be present if you are using agit checkout.

If you are usinggit, you can view the most recent install instructions at:

http://developer.postgresql.org/docs/postgres/installation.html

and the current release notes at:

http://developer.postgresql.org/docs/postgres/release.html

Users compiling fromCVS will also need compatible versions of Bison and

Flex, as discussed in the install documentation.Bison and Flex are not

Users compiling fromgit will also need compatible versions of Bison, Flex,

and Perl, as discussed in the install documentation.These programs are not

needed when using a tarball, since the files they are needed to build are

already present in the tarball.

already present in the tarball. (On Windows, however, you need Perl anyway.)