This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Packaging without disturbing an existing installation
Type: enhancement Stage: resolved
Components: Build Versions: Python 3.0, Python 2.6
process
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: Nosy List: christian.heimes, jackjansen, ronaldoussoren, stmansfield
Priority: low Keywords: patch

Created on 2003-05-07 18:42 by stmansfield, last changed 2022-04-10 16:08 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
Makefile_Destdir.patch.gz stmansfield, 2003-05-07 18:42 Patch to 'Makefile.pre.in' in diff/gz form
Messages (6)
msg53875 - (view) Author: Scott Mansfield (stmansfield) Date: 2003-05-07 18:42
As a developer/maintainer of a custom embedded
GNU/Linux distribution, I need to be able to build and
package various components that make up this operating
system in as convenient, painless manner possible.

One thing that is missing from the Python build process
is the ability to specify an alternate destination
directory for packaging concerns.  To that end, at the
request of one of the 'python-help' volunteers (thanks
Matt!) I am submitting this feature request and patch.

This patch will modify the 'Makefile.pre.in' file,
prepending a DESTDIR in front installation target
directories.  Note that this is pretty much de-facto
standard behavior for most autoconf- automake- type
builds.  This will not alter the 'prefix', 'execprefix'
or other directories that hinge on same.

Once this patch is applied and the sources are
successfully built, one could do a "make
DESTDIR='/opt/pkg' install" and have the installtion
faithfully reproduced under '/opt/pkg' (example
directory only), and create a finished, deployable
package; saving one from having to suffer the pain of
having to pick through /usr, and also saving the pain
of potentially over-writing whatever existing
installation might exist on the build machine.
msg53876 - (view) Author: Jack Jansen (jackjansen) * (Python committer) Date: 2003-05-09 14:00
Logged In: YES 
user_id=45365

I would be interested in this as well, as it would simplify MacOSX binary 
installer building too.

For a quick inspection I also think that the patch isn't complete for MacOSX 
framework builds (where part of the installation is done in Mac/OSX/
Makefile), I will try to find time to test the patch but it could be another 2 
weeks before I get around to it.
msg53877 - (view) Author: Scott Mansfield (stmansfield) Date: 2003-05-09 14:54
Logged In: YES 
user_id=566409

I just had another look at the changes I made to the
Makefile.pre.in, it will /not/ work for Mac OS X at this
time.  I do my development at work on an x86 host, but have
Mac OS X at home.  I'll try to update the patch file this
weekend (5/10/2003) so the 'Framework' makefile target is
properly handled.
msg59252 - (view) Author: Christian Heimes (christian.heimes) * (Python committer) Date: 2008-01-04 19:47
This patch should be considered for Python 2.6 and newer.
msg83151 - (view) Author: Ronald Oussoren (ronaldoussoren) * (Python committer) Date: 2009-03-04 22:34
AFAIK this patch is no longer necessary, at least no on OSX. The current 
binary installer is already build using a separate DESTDIR without having 
to patch Makefiles.
msg92321 - (view) Author: Ronald Oussoren (ronaldoussoren) * (Python committer) Date: 2009-09-06 13:38
Closing this issue, the patch is no longer needed because the current 
Makefiles already have DESTDIR support.
History
Date User Action Args
2022-04-10 16:08:37adminsetgithub: 38460
2009-09-06 13:38:28ronaldoussorensetstatus: open -> closed
resolution: out of date
messages: + msg92321

stage: resolved
2009-03-04 22:34:58ronaldoussorensetnosy: + ronaldoussoren
messages: + msg83151
2008-01-04 19:47:06christian.heimessetpriority: normal -> low
nosy: + christian.heimes
messages: + msg59252
keywords: + patch
versions: + Python 2.6, Python 3.0
2003-05-07 18:42:14stmansfieldcreate