summaryrefslogtreecommitdiffstats
path: root/Mac
diff options
context:
space:
mode:
authorJack Jansen <jack.jansen@cwi.nl>2003-11-20 13:50:28 (GMT)
committerJack Jansen <jack.jansen@cwi.nl>2003-11-20 13:50:28 (GMT)
commitc09857ab7855ac415b73a3c1137014a2fd999b7d (patch)
tree829f2b9a0e4014853f4142c78c40c0eccde05900 /Mac
parent4df306879b4d93112b3bd46f74a73d1b5cd04cca (diff)
downloadcpython-c09857ab7855ac415b73a3c1137014a2fd999b7d.zip
cpython-c09857ab7855ac415b73a3c1137014a2fd999b7d.tar.gz
cpython-c09857ab7855ac415b73a3c1137014a2fd999b7d.tar.bz2
Added some help to OSX/Dist/README.txt, plus all the information
from the OS9 readme that is still relevant. Got rid of Distributions/readme.txt.
Diffstat (limited to 'Mac')
-rw-r--r--Mac/Distributions/readme.txt60
-rw-r--r--Mac/OSX/Dist/README.txt50
2 files changed, 48 insertions, 62 deletions
diff --git a/Mac/Distributions/readme.txt b/Mac/Distributions/readme.txt
deleted file mode 100644
index 1c53766..0000000
--- a/Mac/Distributions/readme.txt
+++ /dev/null
@@ -1,60 +0,0 @@
-How to make a Python-distribution.
-----------------------------------
-
-These notes are mainly for myself, or for whoever tries to make a MacPython
-distribution when I'm fed up with it. They were last updated for 2.3a1.
-
-- Increase fragment version number in PythonCore and PythonCoreCarbon.
- the fragment number is Python's sys.hexversion, it should be set in the
- "PEF" preferences.
-- Increase version number in _versioncheck.py
-- Build PythonStandSmall, run once in root folder
-- Update NEWS, readme's, Demo:build.html
-- fullbuild everything with increase-buildno
-- Test with test.regrtest
-- Update Numeric and build/install it
-- Recompile OSAm and possibly other Contrib stuff
-- mkdistr binary.include
-- mkdistr dev.include
-- make distribution archive with Installer Vise
- Things to make sure of:
- - Version number in toplevel folder name
- - Finder icon positions
- - Version numbers in "Packages..." window
- - Version number in "Installer Settings" -> "Easy Install Text"
- - Version number in "Project" -> Attributes
- - Version number in "Project" -> PostProcess
- - Version number in "Internet" -> "Download Sites"
- - Version number in "Internet" -> "File Groups".
-- Check for missing files. Do this by installing everything on your local system,
- and comparing the file tree (CodeWarrior Compare is great for this) with
- :Mac:Distributions:(vise):binary distribution and ....:dev distribution.
- Only the :Lib:plat-xxxx should be missing. Otherwise go back to Installer Vise and
- add the missing stuff. Make sure of all settings for the new files (esp. "where"
- and "gestalt" are easy to miss).
-- test on virgin systems (both OS9 and OSX).
-- Remove the local installation so you don't get confused by it.
-- checkin everything except PythonX.Y.vct.
-- mkdistr src.include
-- Rename "src distribution" and stuffit
-- Upload
-- Update README file in ftp directory
-- Change version number in public_html/macpythonversion.txt .
-- Update macpython.html
-- Send an announcement to:
- pythonmac-sig@python.org
- python-dev@python.org
-- Wait a day or so for catastrophic mistakes, then send an announcement to:
- python-announce@python.org
- archivist@info-mac.org
- adcnews@apple.com
- news@macnn.com
- http://www.macupdate.com
- http://guide.apple.com/usindex.lasso
- http://www.apple.com/downloads/macosx/submit
- http://www.versiontracker.com/ (userid Jack.Jansen@oratrix.com)
- http://www.macshareware.net (userid jackjansen)
- Also, check out Stephan Deibels http://pythonology.org/market contact list
-- Open PythonX.Y.vct again, use the "remove compressed files" command to trim down
- the size, commit.
-- Remove the subdires under (vise) so you don't get confused by them later. \ No newline at end of file
diff --git a/Mac/OSX/Dist/README.txt b/Mac/OSX/Dist/README.txt
index 89ecd2b..918b15d 100644
--- a/Mac/OSX/Dist/README.txt
+++ b/Mac/OSX/Dist/README.txt
@@ -1,3 +1,49 @@
-This is a set of build scripts and such for MacPython-OSX 2.3 that I
-will use until there are standard distributions from Jack.
+Building a MacPython distribution
+=================================
+The ``build`` shell script here creates MacPython distributions.
+It builds a complete framework-based Python out-of-tree, installs
+it in a funny place with $DESTROOT, massages that installation to remove
+.pyc files and such, creates an Installer package from the installation
+plus the stuff in ``resources`` and compresses that installer as a
+``.dmg`` disk image.
+
+Here are the steps you ned to follow to build a MacPython installer:
+
+- There are various version numbers that need to be updated. Weed through
+ ``Mac/OSXResources``, ``Mac/scripts`` and ``Mac/Tools`` and inspect the
+ various ``.plist`` and ``.strings`` files. Note that the latter are
+ UTF-16 files.
+- Edit ``resource/ReadMe.txt`` and ``resources/Welcome.rtf`` to reflect
+ version number and such.
+- Edit ``build`` to change ``PYVERSION``, ``PYVER`` and ``BUILDNUM``.
+- Run ``./build``. Optionally you can pass the name of the directory
+ where Python will be built, so you don't have to wait for the complete
+ build when you're debugging the process. For the final distribution use
+ a clean build.
+- When done the script will tell you where the DMG image is.
+
+Currently (November 2003) there is still a bug in the build procedure
+for $DESTROOT builds: building some of the applets will fail (in
+``Mac/OSX/Makefile``) if you don't have the same version of Python installed
+normally. So before doing the distribution you should build and install
+a framework Python in the normal way.
+
+When all is done, announcements can be posted to at least the following
+places:
+- pythonmac-sig@python.org
+- python-dev@python.org
+- python-announce@python.org
+- archivist@info-mac.org
+- adcnews@apple.com
+- news@macnn.com
+- http://www.macupdate.com
+- http://guide.apple.com/usindex.lasso
+- http://www.apple.com/downloads/macosx/submit
+- http://www.versiontracker.com/ (userid Jack.Jansen@oratrix.com)
+- http://www.macshareware.net (userid jackjansen)
+
+Also, check out Stephan Deibels http://pythonology.org/market contact list
+
+After all this is done you may also need to update the Package Manager
+database for the new distribution. A description of this remains TBD.