pgsql/src/interfaces/python GNUmakefile

From: Bruce Momjian - CVS <momjian(at)hub(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql/src/interfaces/python GNUmakefile
Date: 2001-05-25 14:29:40
Message-ID: 200105251429.f4PETeW39794@hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

CVSROOT: /home/projects/pgsql/cvsroot
Module name: pgsql
Changes by: momjian(at)hub(dot)org 01/05/25 10:29:39

Modified files:
src/interfaces/python: GNUmakefile

Log message:
The attached patch changes src/interfaces/python/GNUmakefile to use the
value of DESTDIR like the rest (or at least most) of the PostgreSQL
makefiles. I found this problem when trying to package a pre-built
Cygwin PostgreSQL distribution, but this problem is platform independent.

The problem manifests itself when one tries to install into a stagging
area (e.g., to build a tarball) instead of a real install. In this case,
pg.py and _pgmodule$(SO) still end up being installed in the configured
prefix directory ignoring the value of DESTDIR.

Unfortunately, this patch does not handle the case where PostgreSQL
and Python are configured with different prefixes. Since the Python
Makefile is automatically generated and does not use DESTDIR, I believe
that this issue will be difficult to correct. If anyone has ideas on
how to fix this issue, then I'm quite willing to rework the patch to
take the suggestion into account.

Jason Tishler

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian - CVS 2001-05-25 15:32:33 pgsql/src/interfaces/python GNUmakefile
Previous Message Bruce Momjian - CVS 2001-05-25 14:28:58 pgsql/src Makefile.global.in interfaces/jdbc/M ...