This post originated from an RSS feed registered with PHP Buzz
by Jim Reverend.
Original Post: svk to the rescue... or not
Feed Title: revjim.net: PHP Section
Feed URL: http://www.contegix.com/xml/rss20/feed.xml
Feed Description: because a Reverend can't be wrong. Rants, raves, code reviews and programming practice discussions regarding all things PHP.
I’ve got quite a few changes I’d like to make to the Typo blogging engine. Drastic changes that are unlikely to be accepted into the official Typo software partly because I don’t intend to waste any time dealing with the finer points of the consideration of uses other than my own. So, I thought I’d make my own version of Typo Called “TypeO+” (read: Type O Positive).
The easiest way to do this, of course, is to introduce svk into the mix. I can link an SVK repository to both the official Typo SVN and a TypeO+ SVN. Additionally, I can create a 3rd SVN to version the actual website data and files used for my site. Getting new changes from Typo SVN is easy (unless my version becomes so heavily modified that their changes no longer make sense) and keeping TypeO+ offered the the public is also easy.
So… SVK it is then.
Except it doesn’t seem to work on my new host, DreamHost. Ahhh the first nip from the nasty “I’m not managing my own server any more” bug.
The SVK install complains that the SVN installed on DreamHost does not have Perl bindings available and that I’ll need to install them. This, of course, means compiling SVN myself in a local (to my username) directory.
Previous Topic
