On 6 Dec, 2008, at 0:52, Brett Cannon wrote:
On Fri, Dec 5, 2008 at 15:40, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:How does that sounds?Sounds good! Are we also going to produce OSX binaries on a regular basis?Specifically, who is working on binaries for 3.0 and 2.6.1? Ronald? (the 2.6.1 release page claims that they are signed with Benjamin's key, but no binary is even available. Before this gets fixed, I think we need to agree on who is going to produce the binaries, and using what schedule.)What we probably should do is outline the steps in PEP 101 for building the various binaries. For instance I could cut OS X releases but I just don't know the exact steps are.
For 2.5.x I used to following procedure. Requirements: * An Intel Mac running 10.4.x * Have the latest version of XCode for Tiger systems installed * Have Tcl/Tk for OSX installed(Needed to make it possible for people to use a newer Tcl/Tk with Tkinter and IDLE without rebuilding _tkinter themselves. The version of _tkinter that's installed by this procedure also works when Tcl/Tk is not installed on a user's machine).
* Make sure /opt/local and /sw do not exist, to avoid contaminating the build with DarwinPorts/Fink bits
* Use the script in Mac/BuildScript to actually build the installer DMGThis will download a number of components (such as sleepycat DB), builds all required software
and assembles the installer.
I used to test the installer on a 10.3.9 PPC system, a 10.4 system and
a 10.5 system.
Ronald
-Brett _______________________________________________ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
