| Jack Jansen | c09857a | 2003-11-20 13:50:28 +0000 | [diff] [blame] | 1 | Building a MacPython distribution |
| 2 | ================================= |
| Jack Jansen | 8806d47 | 2003-03-21 23:52:36 +0000 | [diff] [blame] | 3 | |
| Jack Jansen | c09857a | 2003-11-20 13:50:28 +0000 | [diff] [blame] | 4 | The ``build`` shell script here creates MacPython distributions. |
| 5 | It builds a complete framework-based Python out-of-tree, installs |
| 6 | it in a funny place with $DESTROOT, massages that installation to remove |
| 7 | .pyc files and such, creates an Installer package from the installation |
| 8 | plus the stuff in ``resources`` and compresses that installer as a |
| 9 | ``.dmg`` disk image. |
| 10 | |
| 11 | Here are the steps you ned to follow to build a MacPython installer: |
| 12 | |
| 13 | - There are various version numbers that need to be updated. Weed through |
| 14 | ``Mac/OSXResources``, ``Mac/scripts`` and ``Mac/Tools`` and inspect the |
| 15 | various ``.plist`` and ``.strings`` files. Note that the latter are |
| 16 | UTF-16 files. |
| 17 | - Edit ``resource/ReadMe.txt`` and ``resources/Welcome.rtf`` to reflect |
| 18 | version number and such. |
| 19 | - Edit ``build`` to change ``PYVERSION``, ``PYVER`` and ``BUILDNUM``. |
| 20 | - Run ``./build``. Optionally you can pass the name of the directory |
| 21 | where Python will be built, so you don't have to wait for the complete |
| 22 | build when you're debugging the process. For the final distribution use |
| 23 | a clean build. |
| 24 | - When done the script will tell you where the DMG image is. |
| 25 | |
| 26 | Currently (November 2003) there is still a bug in the build procedure |
| 27 | for $DESTROOT builds: building some of the applets will fail (in |
| 28 | ``Mac/OSX/Makefile``) if you don't have the same version of Python installed |
| 29 | normally. So before doing the distribution you should build and install |
| 30 | a framework Python in the normal way. |
| 31 | |
| 32 | When all is done, announcements can be posted to at least the following |
| 33 | places: |
| 34 | - pythonmac-sig@python.org |
| 35 | - python-dev@python.org |
| 36 | - python-announce@python.org |
| 37 | - archivist@info-mac.org |
| 38 | - adcnews@apple.com |
| 39 | - news@macnn.com |
| 40 | - http://www.macupdate.com |
| 41 | - http://guide.apple.com/usindex.lasso |
| 42 | - http://www.apple.com/downloads/macosx/submit |
| 43 | - http://www.versiontracker.com/ (userid Jack.Jansen@oratrix.com) |
| 44 | - http://www.macshareware.net (userid jackjansen) |
| 45 | |
| 46 | Also, check out Stephan Deibels http://pythonology.org/market contact list |
| 47 | |
| 48 | After all this is done you may also need to update the Package Manager |
| 49 | database for the new distribution. A description of this remains TBD. |