Dirkjan Ochtman wrote: > On 05/04/2009 11:06, "Martin v. Löwis" wrote: >> In particular, the Stackless people have requested that they move along >> with what core Python does, so their code should also be converted. > > I'd be interested to hear if they want all of their stuff converted, or > just the mainline/trunk of what is currently in trunk/branches/tags. Richard Tew would be the person discuss the details with. >> - integrate with the buildbot > > I've setup the buildbot infra for Mercurial (though not many people are > interesting in it, so it's kind of languished). Using buildbot's hg > support is easy. 0.7.10 is the first version which works with hg 1.1+, > though, so we probably don't want to go with anything earlier. Ok, that's a problem. We currently run 0.7.5 on the master, and have made custom changes that need to be forward-ported. IIUC, this will also mean that the waterfall default page is gone, which might surprise people. I suppose all slaves also need to upgrade. >> - come up with a strategy for /external (also relevant for >> the buildbot slaves) > > I'm not sure exactly what the purpose or mechanism for /external is. > Sure, it's like a snapshot dir, probably used for to pull some stuff > into other process? Seems to me like it might be interesting to, for > example, convert to a simple config file + script that lets you specify > a package (repository) + tag, which can then be easily pulled in. > > But it'd be nice to know where and how exactly this is used. Take a look at the batch files in Tools/buildbot - they are the primary consumers. PCbuild/readme.txt also refers to it. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4