In Eclipse I have every project checked out in ~/workspace/ so every directory with the matching server root would need to be switched. This shell script handled all the svn switch –relocate statements for me. Replace oldservername and newservername.

for dir in `ls -1 */.svn/entries | xargs grep -H -l oldservername | grep -E -o "^[^\/]+"`; do
svn switch --relocate `svn info $dir | grep ^Repository\ Root | cut -f 3 -d ' '` `svn info $dir | grep ^Repository\ Root | cut -f 3 -d ' ' | sed 's/oldservername/newservername/'` $dir
done

It may be best to make a backup of your project directories, especially if you have local uncommitted changes. This script works on bash-like command lines, such as Mac OS X.

“When the Union Delegates called upon me to insist that none but men who had seven years’ apprenticeship should be employed in the works, I told them that I preferred employing a man who had acquired the requisite mechanical skill in two years rather than another who was so stupid as to require seven years’ teaching. The delegates regarded this statement as preposterous and heretical. In fact, it was high treason. But in the long run we carried our point.”

James Nasmyth: Engineer; an autobiography by James Nasmyth

Meetup if you’re interested.

On my machine I use Eclipse which stores files in ~/workspace/ – all of my paths are based off of this, and I add an alias to apache so that all my eclipse projects are available at http://localhost/workspace/{project}

For my setup, I have checked out the validator source code in ~/workspace/validator/ which shows up at http://localhost/workspace/validator/. Modify the paths if your CVS checkout is in a different location.

To get a snapshot of the latest files for the validator you can use:
cvs -d :pserver:anonymous:anonymous@dev.w3.org:/sources/public checkout validator, which will create a validator directory with the latest files.

Make sure your apache configuration has includes enabled, and will process the cgi script — modify the /etc/apache2/apache2.conf file — sudo nano /etc/apache2/apache2.conf, and add the following:

# This is the directory where you have the validator's "check"
# script as well as its and *.html, *.css etc files.

<Location "/workspace/validator/htdocs/check">
SetHandler cgi-script
</Location>


Then, in the CVS files you have checked out, symbolically link the ‘check’ file within the htdocs directory:

cd htdocs
ln -s ../httpd/cgi-bin/check check

So that the file check -> ../httpd/cgi-bin/check


cd ../httpd
chmod +x check


Install the modules and dependencies:

sudo apt-get install opensp xmlto
sudo cpan install Config::General Encode::HanExtra Encode::JIS2K HTML::Encoding HTML::Template Test::Exception Class::Accessor Test::Builder Sub::Uplevel Test::Builder::Tester
wget http://superb-west.dl.sourceforge.net/sourceforge/openjade/OpenSP-1.5.2.tar.gz
gunzip OpenSP-1.5.2.tar.gz
tar -xvf OpenSP-1.5.2.tar
cd OpenSP-1.5.2
./configure
make
sudo make install
sudo cpan install SGML::Parser::OpenSP XML::LibXML Net::IP


And I refuse to use it. I’ve seen it’s features, it does have a decent template system, but I feel like 75% of it is feature overkill. Not to mention a ton of code which could be simplified by just using a few PEAR packages.

To those people that like it, that’s fine… go a head and use it. But I’m not interested in using some huge app for what should be a tiny blog system. I want something PEAR installable, uses PDO, PHP5 compliant, and most importantly – simple.

So I’m starting work on the salty blog system… it’s a derivative of my current site. It’ll have all the standard blog software bull: multi-users, commenting, categories, archives, fully customizable templates etc. But it’s not going to be huge, and it will be easy to install and upgrade.

It uses:

• MDB2_Schema
• DB_DataObject
• Savant3
• maybe FormBuilder

and most importantly, it will be PEAR installable and upgradable. I plan on using it here at home for my personal site, and at work to start documenting some of the work things I do and foster some communication between coworkers. So stay tuned if you care, or don’t – I don’t care…. but one things for sure.

I ain’t no WP sellout.

Thank you for accompanying me on this journey, as we travel into the unknown.
….more will follow.

-Brett