blob: d883c95e85b989b826389e2010a999d5e4168a47 [file] [log] [blame]
Jeremy Hylton355e2f22000-10-16 15:34:52 +00001This directory contains support file used to build RPM releases of
Guido van Rossum23105d52002-01-06 03:29:16 +00002Python. Its contents are maintained by Sean Reifschneider
3<jafo@tummy.com>.
Jeremy Hylton355e2f22000-10-16 15:34:52 +00004
Anthony Baxterfd95c3a2003-09-24 01:36:13 +00005If you wish to build RPMs from the base Python release tar-file, note
6that you will have to download the
7"doc/<version>/html-<version>.tar.bz2"
8file from python.org and place it into your "SOURCES" directory for
9the build to complete. This is the same directory that you place the
10Python-2.3.1 release tar-file in. You can then use the ".spec" file in
11this directory to build RPMs.
Sean Reifscheider9aad7fe2010-11-07 21:26:53 +000012
13You may also wish to pursue RPMs provided by distribution makers to see if
14they have one suitable for your uses. If, for example, you just want a
15slightly newer version of Python than what the distro provides, you could
16pick up the closest SRPM your distro provides, and then modify it to
17the newer version, and build that. It may be as simple as just changing
18the "version" information in the spec file (or it may require fixing
19patches).
20
21NOTE: I am *NOT* recommending just using the binary RPM, and never do an
22install with "--force" or "--nodeps".
23
24Also worth pursuing may be newer versions provided by similar distros. For
25example, a Python 3 SRPM from Fedora may be a good baseline to try building
26on CentOS.
27
28Many newer SRPMs won't install on older distros because of format changes.
Brian Curtinab19bd42010-11-07 22:09:05 +000029You can manually extract these SRPMS with:
Sean Reifscheider9aad7fe2010-11-07 21:26:53 +000030
31 mkdir foo
32 cd foo
33 rpm2cpio <../python3-*.src.rpm | cpio -ivd