OK, I've checked in the first steps of the rules project; namely, created the rules "trunk", created an svn:external link to that from the existing project trunk, and created the first draft of a rules compiler.
The next step is to perform the renames -- moving some of the core rules files from code trunk into the new rules trunk. Here's the script I'll be running: http://taint.org/xfer/2005/svnrenames I plan to do this in a day or two, assuming nobody objects. lazy consensus now applies ;) The svn:external property uses the https:// URL for the rulesrc repository location. This seems to be unavoidable; one, and only one, absolute URL must be used here, and in my opinion it needs to be editable by committers to be useful. It seems buildbot has some difficulty, unfortunately; it gives Error validating server certificate for 'https://svn.apache.org:443': - The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually! Certificate information: - Hostname: svn.apache.org - Valid: from Jan 26 14:18:55 2005 GMT until Jan 26 14:18:55 2007 GMT - Issuer: http://www.starfieldtech.com/repository, Starfield Technologies, Inc., Scottsdale, Arizona, US - Fingerprint: 19:51:6b:9b:03:78:2b:4b:0f:02:77:ed:2a:85:ef:93:ed:b6:ff:95 (R)eject, accept (t)emporarily or accept (p)ermanently? which needs to be (manually) accepted for each slave. If anyone can see an SVN-level fix for this, I'd love to hear it.... --j.
