summaryrefslogtreecommitdiffstats
path: root/Makefile.pre.in
diff options
context:
space:
mode:
authorNeil Schemenauer <nascheme@enme.ucalgary.ca>2001-02-16 04:16:34 (GMT)
committerNeil Schemenauer <nascheme@enme.ucalgary.ca>2001-02-16 04:16:34 (GMT)
commit2b2681ac3eaef1382315806d049789a54ec5e177 (patch)
tree1285dd98c47e8d6e86551f91b69b5c736e1b3e87 /Makefile.pre.in
parent28aa9d39b056604ceeee2ee5c637c05ebb3248f3 (diff)
downloadcpython-2b2681ac3eaef1382315806d049789a54ec5e177.zip
cpython-2b2681ac3eaef1382315806d049789a54ec5e177.tar.gz
cpython-2b2681ac3eaef1382315806d049789a54ec5e177.tar.bz2
Remove confusing explaination about altinstall target and refer to
the README file.
Diffstat (limited to 'Makefile.pre.in')
-rw-r--r--Makefile.pre.in17
1 files changed, 2 insertions, 15 deletions
diff --git a/Makefile.pre.in b/Makefile.pre.in
index fa8fc52..c1279f4 100644
--- a/Makefile.pre.in
+++ b/Makefile.pre.in
@@ -13,21 +13,8 @@
#
# If you have a previous version of Python installed that you don't
# want to overwrite, you can use "make altinstall" instead of "make
-# install". This changes the install procedure so it installs the
-# Python binary as "python<version>". The libraries and include files
-# are always installed in a subdirectory called "python<version>".
-# "make altinstall" does not install the manual page. If you want to
-# make this installation the "official" installation but want to keep
-# the old binary around "just in case", rename the installed python
-# binary to "python<oldversion>" before running "make install".
-# (This only works between different versions, e.g. 1.3 and 1.4 --
-# different betas of the same version will overwrite each other in
-# installation unless you override the VERSION Make variable.)
-#
-# In fact, "make install" or "make bininstall" installs the binary
-# as python<version> and makes a hard link to python, so when
-# installing a new version in the future, nothing of the current
-# version will be lost (except for the man page).
+# install". Refer to the "Installing" section in the README file for
+# additional details.
#
# See also the section "Build instructions" in the README file.