Win32 packages released on sourceforge

Paul Millar paulm at astro.gla.ac.uk
Tue Mar 23 12:56:07 CST 2004


Hi Dimi,

I guess we have to agree to disagree on this one.  I still think that
synchronous message-passing in distributed systems is a recipe for
disaster (asynchronous is the only way to go).  So schedule me a "told you
so" email a few months after the winetest.exe goes live ;^)

OK, so what I'll do is finalise things here and set up a cron job (at 10am
localtime) to build winetest.exe and publish the results somewhere.  That
should be fairly simple.  The rest is just a matter of agreeing what to
put where and how to register new binaries.  The on-demand builds will
continue (as they might as well) and kept somewhere separate.

I'm GPG-signing all the binaries, as this is trivial for me to do and
should help improve security a bit.  The auto-signing key doesn't have a
pass-phrase (so its only as good as the integrity of the machine), but
that's true for auto-built binaries anyway.  I'll sign the auto-signing
key with my own key (available from my web site) and publicly announce it
soon.

I'm no GPG expert, but does that sound OK?

Paul.

PS
Just as an aside, when do people in the US change their clocks?  Everyone
in the EU is changing to DLS-time (BST in the UK) this Sunday.


On Mon, 22 Mar 2004, Dimitrie O. Paun wrote:
> On Mon, 22 Mar 2004, Paul Millar wrote:
> > > Yes, I meant EST. Or, as you can see from your graph, 10am GMT is
> > > perfect.
> > 
> > OK.  Its also the most likely time by which Alexandre has committed
> > all the patches for that night (although it doesn't guarantee it).  
> > If we had to have a fixed build time, its the best time; but I
> > wouldn't describe it as perfect (but maybe that's just me being
> > awkward :^)
> 
> Whatever you want to call it, but yes, 10am GMT is the most natural
> end/begin of the 24h cycle. It seems to be a rather good choice.
> 
> As for the issue of nighly build vs. randomly initiated build: we can
> argue till the cows come home. It seems that we have different points
> of view. If you want to have CVS-triggered builds for WRT, all the power
> to you, they makes sense in that (controlled) environment. For the nightly
> builds however, I would really like having a build that's kicked off at
> a precise moment in time (and as we discussed, 10GMT seems a good choice).
> 
> Please try to understand that as a developer on Wine, having this extra
> variability adds _nothing_ but headache. It makes it harder to think about
> the problem, to talk about it, to script for it, etc. I don't need it, and
> I don't want it.

----
Paul Millar





More information about the wine-devel mailing list