Ignore:
Timestamp:
Mar 19, 2014, 11:31:01 PM (11 years ago)
Author:
dmik
Message:

python: Merge vendor 2.7.6 to trunk.

Location:
python/trunk
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • python/trunk

  • python/trunk/Doc/distutils/builtdist.rst

    r2 r391  
    8181| ``tar``     | tar file (:file:`.tar`)      | \(3)    |
    8282+-------------+------------------------------+---------+
    83 | ``zip``     | zip file (:file:`.zip`)      | \(4)    |
     83| ``zip``     | zip file (:file:`.zip`)      | (2),(4) |
    8484+-------------+------------------------------+---------+
    8585| ``rpm``     | RPM                          | \(5)    |
     
    8989| ``sdux``    | HP-UX :program:`swinstall`   |         |
    9090+-------------+------------------------------+---------+
    91 | ``rpm``     | RPM                          | \(5)    |
    92 +-------------+------------------------------+---------+
    93 | ``wininst`` | self-extracting ZIP file for | (2),(4) |
     91| ``wininst`` | self-extracting ZIP file for | \(4)    |
    9492|             | Windows                      |         |
    9593+-------------+------------------------------+---------+
     94| ``msi``     | Microsoft Installer.         |         |
     95+-------------+------------------------------+---------+
     96
    9697
    9798Notes:
     
    102103(2)
    103104   default on Windows
    104 
    105    **\*\*** to-do! **\*\***
    106105
    107106(3)
     
    134133| :command:`bdist_wininst` | wininst               |
    135134+--------------------------+-----------------------+
     135| :command:`bdist_msi`     | msi                   |
     136+--------------------------+-----------------------+
    136137
    137138The following sections give details on the individual :command:`bdist_\*`
     
    144145=================================
    145146
    146 **\*\*** Need to document absolute vs. prefix-relative packages here, but first
    147 I have to implement it! **\*\***
     147.. XXX Need to document absolute vs. prefix-relative packages here, but first
     148       I have to implement it!
    148149
    149150
     
    174175
    175176   python setup.py bdist_rpm --packager="John Doe <jdoe@example.org>" \
    176                    bdist_wininst --target_version="2.0"
     177                   bdist_wininst --target-version="2.0"
    177178
    178179Creating RPM packages is driven by a :file:`.spec` file, much as using the
     
    239240you distribute or package many Python module distributions, you might want to
    240241put options that apply to all of them in your personal Distutils configuration
    241 file (:file:`~/.pydistutils.cfg`).
     242file (:file:`~/.pydistutils.cfg`).  If you want to temporarily disable
     243this file, you can pass the --no-user-cfg option to setup.py.
    242244
    243245There are three steps to building a binary RPM package, all of which are
     
    319321
    320322By default the installer will display the cool "Python Powered" logo when it is
    321 run, but you can also supply your own bitmap which must be a Windows
     323run, but you can also supply your own 152x261 bitmap which must be a Windows
    322324:file:`.bmp` file with the :option:`--bitmap` option.
    323325
     
    355357To cross-compile, you must download the Python source code and cross-compile
    356358Python itself for the platform you are targetting - it is not possible from a
    357 binary installtion of Python (as the .lib etc file for other platforms are
     359binary installation of Python (as the .lib etc file for other platforms are
    358360not included.)  In practice, this means the user of a 32 bit operating
    359361system will need to use Visual Studio 2008 to open the
     
    372374---------------------------
    373375
    374 Starting with Python 2.3, a postinstallation script can be specified which the
     376Starting with Python 2.3, a postinstallation script can be specified with the
    375377:option:`--install-script` option.  The basename of the script must be
    376378specified, and the script filename must also be listed in the scripts argument
     
    425427   Which folders are available depends on the exact Windows version, and probably
    426428   also the configuration.  For details refer to Microsoft's documentation of the
    427    :cfunc:`SHGetSpecialFolderPath` function.
     429   :c:func:`SHGetSpecialFolderPath` function.
    428430
    429431
Note: See TracChangeset for help on using the changeset viewer.