Very cool, Trent! I also love the retro use of svn as a tie-in to how long you have been fighting to bring this project to fruition. =)<br><br><div class="gmail_quote">On Tue, Sep 11, 2012 at 8:20 AM, Trent Nelson <span dir="ltr"><<a href="mailto:trent@snakebite.org" target="_blank">trent@snakebite.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Quick start:<br>
<br>
% cd ~ && svn co <a href="http://svn.snakebite.net/.snakebite" target="_blank">http://svn.snakebite.net/.snakebite</a> && cd .snakebite && sh snakebite.subr<br>
<br>
If all goes well, you should see something like this:<br>
<br>
A .snakebite/snakebite.subr<br>
A .snakebite/ssh_config_ext<br>
A .snakebite/ssh_known_hosts<br>
U .snakebite<br>
Checked out revision 58.<br>
Created link for 'sb'.<br>
Created link for 'sbx'.<br>
Created link for 'sby'.<br>
Created link for 'sbctl'.<br>
Fixed permissions for /Users/Trent/.snakebite/snakebite.subr.<br>
The following commands can now be executed directly:<br>
sb<br>
sbx<br>
sby<br>
sbctl<br>
Testing connection.........done.<br>
Getting a list of your projects...done.<br>
Looking up your username for project 'cpython'...done.<br>
Getting project details for 'trent.nelson@cpython'...done.<br>
Setting current project to 'cpython'...done.<br>
Trent, you're now configured for cpython. Enjoy!<br>
+---------------------------------------+<br>
| Available Hosts |<br>
| (Last Update: 2012-09-11 11:08:01Z) |<br>
+---------------------------------------+<br>
| Alias | OS | Arch |<br>
+-------|--------------------|----------+<br>
| a7|AIX 7.1 | Power4 |<br>
| d3|DragonFlyBSD 3.0.2 | x64 |<br>
| d3x|DragonFlyBSD 3.0.2 | x86 |<br>
| h2|HP-UX 11iv2 | PA-RISC |<br>
| h3|HP-UX 11iv3 | Itanium2 |<br>
| i6|IRIX 6.5.30 | MIPS |<br>
| n51|NetBSD 5.1.2 | x64 |<br>
| n51x|NetBSD 5.1.2 | x86 |<br>
| o51x|OpenBSD 5.1 | x86 |<br>
| o51|OpenBSD 5.1 | x64 |<br>
| s10|Solaris 10 | SPARC |<br>
| s9|Solaris 9 | SPARC |<br>
+---------------------------------------+<br>
Enter alias:<br>
<br>
Simply enter any of the aliases in the table and it'll ssh you into<br>
that box as cpython@, i.e.:<br>
<br>
Enter alias: a7<br>
AIX arsenic 1 7 000BF95F4C00<br>
<br>
:::. :::::::.. .::::::. .,:::::: :::. :::. ::: .,-:::::<br>
;;`;; ;;;;``;;;; ;;;` ` ;;;;'''' `;;;;, `;;; ;;; ,;;;'````'<br>
,[[ '[[, [[[,/[[[' '[==/[[[[, [[cccc [[[[[. '[[ [[[ [[[<br>
c$$$cc$$$c $$$$$$c ''' $ $$"""" $$$ "Y$c$$ $$$ $$$<br>
888 888, 888b "88bo, 88b dP 888oo,__ 888 Y88 888 `88bo,__,o,<br>
YMM ""` MMMM "W" "YMmMY" """"YUMMM MMM YM MMM "YUMMMMMP"<br>
<br>
AIX 7.1<br>
IBM IntelliStation 9114-275<br>
2 x 1.4GHz Power4 CPUs<br>
2 x 2Gbps LP9802 FC HBAs<br>
8GB RAM, 4 x 36GB<br>
<br>
[cpython@arsenic]~%<br>
<br>
General notes:<br>
<br>
- Almost all of the hosts have a corresponding cpython build slave,<br>
which always lives in ~/buildslave.<br>
<br>
- You're more than welcome to set up local builds on each box.<br>
Keep everything in ~/hg. Some hosts already have a ~/hg dir,<br>
others don't. The layout should be:<br>
<br>
~/hg/3.x<br>
~/hg/3.2<br>
~/hg/2.7<br>
<br>
If they don't exist, feel free to create them. It's going to<br>
be easiest to just clone the corresponding build directory<br>
from ~/buildslave, i.e. if you want a local 3.x area but no<br>
~/hg/3.x exists:<br>
<br>
% cd ~/hg<br>
% hg clone ~/buildslave/3.x-*/build 3.x<br>
<br>
Once a base repo has been created, you can clone a local copy:<br>
hg clone 3.x 3.x.trent.issue2811<br>
<br>
Try follow that naming convention as it'll make it easier for<br>
other developers to figure out what each directory is for.<br>
<br>
Also, try and keep tabs on local builds and remove things you<br>
don't need once you're done. I haven't finished hooking up<br>
the SAN yet so everything is on local disks at the moment;<br>
disk space is a bit light in some places.<br>
<br>
- If you're not used to vi shell key bindings, you're going to<br>
have a bad time :-)<br>
<br>
- Almost all of the hosts (except for the *BSDs) have been set<br>
up to use a common ~/.zsh and ~/.vim:<br>
http:/<a href="http://svn.snakebite.net/home/trunk/" target="_blank">svn.snakebite.net/home/trunk/</a><br>
http:/<a href="http://svn.snakebite.net/skel/trunk/" target="_blank">svn.snakebite.net/skel/trunk/</a><br>
They're both based on random dotfile hacking I've done over<br>
the years and are far from elegant -- so, suggestions welcome.<br>
<br>
If I'm awake and working, I'll be on #python-dev, so that'll be the<br>
best place to get me if you need immediate assistance.<br>
<br>
So, log in and have a play around! Oh, X11 forwarding works, too,<br>
just invoke `sbx` (or `sby`) instead of `sb` and it'll invoke ssh<br>
with -X or -Y respectively. All the proprietary UNIX hosts have<br>
X11 installed, complete with glorious circa-late-nineties Motif<br>
eye candy.<br>
<br>
For those looking for tangible things to do... take a look at the<br>
current buildslaves with [SB] in the name -- almost all of them are<br>
failing in some way/shape/form, so there's plenty of stuff to get<br>
your teeth stuck into :-)<br>
<br>
<br>
Trent.<br>
_______________________________________________<br>
Python-Dev mailing list<br>
<a href="mailto:Python-Dev@python.org">Python-Dev@python.org</a><br>
<a href="http://mail.python.org/mailman/listinfo/python-dev" target="_blank">http://mail.python.org/mailman/listinfo/python-dev</a><br>
Unsubscribe: <a href="http://mail.python.org/mailman/options/python-dev/brett%40python.org" target="_blank">http://mail.python.org/mailman/options/python-dev/brett%40python.org</a><br>
</blockquote></div><br>