Martin v. Löwis mar...@v.loewis.de writes:
I do currently have a DMG built for 2.7 Beta 1, if it would be useful.
As I said before: if you would plan to do this on a regular basis, for
all upcoming releases, that would certainly be a good thing.
No argument - just figured I'd offer to get
Martin v. Löwis mar...@v.loewis.de writes:
This actually happened on Windows - some people now
recommend to run the buildbot scripts on a regular developer checkout,
because they supposedly do the right things.
I have to admit that I'm guilty of this (though to be fair
David Bolen wrote:
Martin v. Löwis mar...@v.loewis.de writes:
This actually happened on Windows - some people now
recommend to run the buildbot scripts on a regular developer checkout,
because they supposedly do the right things.
I have to admit that I'm guilty of
Ronald Oussoren ronaldousso...@mac.com writes:
Speaking of which... I have a mac-mini that could be used for a
buildbot. How much work is needed to kickstart a buildbot, taking
into account that I'd prefer to have a buildbot with different
configure-flags that the default unix build (that is,
On Thu, Apr 15, 2010 at 3:54 AM, s...@pobox.com wrote:
Bill In any case, they shouldn't be needed on buildbots maintained by
Bill the PSF.
Sure. My question was related to humans building binary distributions
though. Unless that becomes fully automated so the release manager can
In the first builds, I have noticed that the build master seems to
execute the builds as a Unix system, so isn't building with the
universalsdk option or as a framework, though the latter would
probably need a bit of glue to make the framework available just
locally to the buildbot process.
Martin v. Löwis mar...@v.loewis.de writes:
Not sure what you mean by make available - I thought this is just a
matter of configure options?
Building as a framework, yes. But I think there's some steps to take
to then have the test python binary use the locally built framework
while running
Keeping the knowledge in the makefile or script in the source tree would
let the rules change across branches without affecting the build master.
Though if having more specific rules in the master was easier, I'd be
fine with that too.
Intuitively, I find the set of batch files used for
Martin v. Löwis wrote:
Wasn't that problem fixed weeks ago? The installer image has been
available there since several days after the release. And the link
seems fine now.
The inherent problem remains. There is no binary for 2.7b1, for example.
The last binaries produced in the 2.7
On Thu, Apr 15, 2010 at 12:47:50AM +1000, Nick Coghlan wrote:
Martin v. L?wis wrote:
Wasn't that problem fixed weeks ago? The installer image has been
available there since several days after the release. And the link
seems fine now.
The inherent problem remains. There is no binary
On Wednesday, April 14, 2010, at 04:47PM, Nick Coghlan ncogh...@gmail.com
wrote:
Martin v. Löwis wrote:
Wasn't that problem fixed weeks ago? The installer image has been
available there since several days after the release. And the link
seems fine now.
The inherent problem remains.
I seem to recall there was some issue (aside from the current lack of a
reliable OS X buildbot) that prevented us from regularly grabbing the
head of the tree and using it to automatically build the Windows and Mac
installers (to check that the installers could actually be created,
preventing
Speaking of which... I have a mac-mini that could be used for a
buildbot. How much work is needed to kickstart a buildbot, taking
into account that I'd prefer to have a buildbot with different
configure-flags that the default unix build (that is, I want to test
a framework build that is a
Probably fine on your personal Mac. And the build scripts can probably
mask those out on their own.
For a private Python installation, it doesn't actually hurt to have them
on disk. The binaries may be linked with strange libraries, but it
should work since the libraries themselves are also on
Bill In any case, they shouldn't be needed on buildbots maintained by
Bill the PSF.
Sure. My question was related to humans building binary distributions
though. Unless that becomes fully automated so the release manager can just
push a button and have it built on and
Martin On the slave, you need to install buildbot, and create a slave
Martin configuration; it would the be good if the slave process would
Martin somehow get restarted automatically after a system reboot (I
Martin think there are recipes for that out there).
A static IP address
Making the Windows binary build process automatic and robust is challenging
if you hate Windows (like I do). Martin also made the point that it's
been broken forever, so people don't seem to care :). ISTR Martin just
makes them manually.
That's true. In particular, people had been asking
(ISTM the same might be true should people ever decide to once again build a
Solaris installer. /opt/sfw is currently searched for Berkeley DB include
files.)
And rightly so (likewise for Fink). Primarily, the script is there to
help people installing Python; packaging Python can be more
On 14 April 2010 20:02, s...@pobox.com wrote:
I ran a Mac OSX buildbot for the community buildbots for awhile but never
did figure out at the time how to get it to fire up on reboot. That was a
few years ago. I think today that would easily be accomplished with an
@reboot crontab entry.
On Apr 14, 2010, at 3:30 PM, Simon Brunning wrote:
On 14 April 2010 20:02, s...@pobox.com wrote:
I ran a Mac OSX buildbot for the community buildbots for awhile but never
did figure out at the time how to get it to fire up on reboot. That was a
few years ago. I think today that would
On 14 Apr, 2010, at 19:41, s...@pobox.com wrote:
Ronald Creating the Mac installer is easy: just run
Ronald Mac/BuildScript/build-installer.py on an OSX 10.5 system where a
Ronald local version of Tcl/Tk 8.4 is installed in
Ronald /Library/Frameworks. The system should also not
On 14 Apr, 2010, at 20:46, Martin v. Löwis wrote:
Speaking of which... I have a mac-mini that could be used for a
buildbot. How much work is needed to kickstart a buildbot, taking
into account that I'd prefer to have a buildbot with different
configure-flags that the default unix build (that
I ran a Mac OSX buildbot for the community buildbots for awhile but
never did figure out at the time how to get it to fire up on
reboot. Â That was a few years ago. Â I think today that would easily
be accomplished with an @reboot crontab entry. Â Dunno if that was
How would that work? Creation of the OSX installer is not integrated
in the regular Makefiles but is a separate script.
Again by setting up another builder (and assigning it to either the same
or a different slave). Instead of the regular configure/make/make
test/make clean builder, this one
Martin v. Löwis wrote:
I seem to recall there was some issue (aside from the current lack of a
reliable OS X buildbot) that prevented us from regularly grabbing the
head of the tree and using it to automatically build the Windows and Mac
installers (to check that the installers could actually
s...@pobox.com wrote:
Now that I think about it, it might not be sufficient to just hide those
directories from the environment. The Python setup.py file has
unconditional hard-coded references to /sw, /opt/local and /usr/local. That
I added that to my virus scanner: check any setup.py
Bill Janssen writes:
Fink or MacPorts are often a practical necessity.
Fink is deadly, MacPorts much more benign, in my experience. Which is
several years out-of-date, before I realized I didn't need either one of
them, and before the UNIX community started adding configure patches
27 matches
Mail list logo
