• Vote on Oct 14!

  

• Search for:
• 
  This work is licensed under a Creative Commons Attribution 2.5 Canada License.

• Similar Posts

  • Automatically backing up multiple Subversion repositories
  • XCode 1.5
  • Morning task: Install Subversion Server
  • Learning Object Creation/Editing
  • Subversion, WebSVN and RSS

• Pages

  • About
    • Bookshelf
    • Colophon
    • Contact
    • Music
    • My (not so) Secret Identities
    • Presentations
  • Archives
  • Asides
  • Photos

• My Other Places

  • Mindfulseeing.com (photoblog)
  • Flickr/dnorman
  • Teaching & Learning Centre
  • The University of Calgary

• Recent Comments

  • Mike Caulfield on Ingesting Open Content into a Course Blogsite
  • dnorman on mobile (R/C) video with Flip
  • Is there such a thing as “too open”? « Open Education News on Is there such a thing as “too open”?
  • Jason on mobile (R/C) video with Flip
  • Mike Caulfield on Is there such a thing as “too open”?

• Meta

  • Log in
  • Entries RSS
  • Comments RSS
  • WordPress.org

Looks like our Subversion repository got a bit corrupted today. Here’s the instructions to restore, for future quick reference:

During our latest Pachyderm development sessions, that pesky EOModeler-deletes-the-.svn-directory issue reared it’s ugly head. I was using the workaround (rename the “good” eomodel file, checkout a new one, move the .svn from the new copy to the “good” copy, nuke the new one, rename the “good” one back to the proper filename), and I accidentally deleted the “good” model file - blowing away a couple hours of carefully saved work. Doh.

King to the rescue! He just whipped up the EOModeler SVN Patch Application Enhancer to prevent the nuking of the .svn directory within the .eomodeld directory.

If you use WebObjects and Subversion, grab a copy of this patch! It will save you time, grief, and grey hair.

UPDATE: King just sent me a URL to another project that does the same fix-EOModeler thing… This one was created waaaay back in February 2003. Doh.

UPDATE 2: Another way may have been to use the rmm utility that moves things to the Trash instead of nuking them instantly… I’ve installed rmm, and will try to be using it instead of a forced recursive sudo root rm command. Sure, it’s like having training wheels, but also like having a safety net

I just put together an updated installer for APOLLO’s supporting frameworks and resources. PackageMaker on MacOSX makes it so brain-dead simple to create really powerful installers. Gotta love that. And, it’s free (included with the Developer tools).

This version of the installer includes the Pachyderm PXFoundation and PXPublisher frameworks. (Less than subtle hint about project relationships in there somewhere… )

The installer itself isn’t public yet (just for the developers on the project for now - makes it easier to get a new dev. box up to speed without having to manually compile a raftload of frameworks first).

OK. This doesn’t kill the love-fest that is Subversion, but here’s a Stupid Subversion Behaviour that would be cool if it wasn’t needed… WebObjects database models are stored in bundles (eg., mydatabasemodel.eomodeld) which are actually directories rather than files. Subversion isn’t greatly aware of what to do with these files/collections, so it doesn’t currently do much versioning (i.e., I can’t check in changes made to a model!)

From MacDevCenter.com: Making the Jump to Subversion:

% mv MyModel.eomodeld MyModel.mine
% svn update MyModel.eomodeld
% mv MyModel.eomodeld/.svn MyModel.mine/
% rm -r MyModel.eomodeld
% mv MyModel.mine MyModel.eomodeld

A quick Google turned up some results, but no solutions:

• Collections in Subversion. Part 1 of 2: History [Long]
• Collections in Subversion. Part 2 of 2: Request for Comment

OK, I officially love Subversion. I’ve got the Subversion repository working great, and just installed the WebSVN web interface to it. It’s got RSS feeds all over the place! Now, I can keep up to date on all commits to all files in all projects managed by the source repository - in my RSS reader! This is too cool

WebSVN gives a very cool interface to browse source code trees, viewing aggregate lists of commit comments for all files in that section of the tree. Very handy. Keep up to date from 10,000 feet by viewing comments on / - or keep up to date on just a particular file by looking at just that file.

After getting Subversion running, I have to say how nice it is to work with. I’d missed versioning from my previous attempt with CVS - it’s great to be able to diff against the latest version of a file, or to track changes in general. And FileMerge rocks for visual diff-ing of files.

It would be nice, though, if XCode didn’t need to commit the .pbxuser file every time I open a project… (I know - ignore the update request, but it’s sitting there with that little “M”, silently nagging for an update…

I’ve now got the entire APOLLO codebase in there, and the beginning of the Pachyderm codebase as well. I REALLY like how specific and general you can get with file checkouts. I can get a single file, a single project, or an entire repository with one command. Sweet.

My Big Task for the morning is installing a Subversion server for management of APOLLO and Pachyderm source code. I’ll be installing it onto a shiny new XServe running MacOSX 10.3.5 (just installing the latest patches now…).

Here’s a list of resources I’ll be drawing on today:

• MacDevCenter.com: Making the Jump to Subversion
• subversion.tigris.org - official subversion client - what I used.
• Version Control with Subversion - Oreilly
• Version Control with Subversion - Red Bean
• Metissian - Projects - Mac OS X Packages - Subversion - unofficial subversion client - had less luck with this.
• Bill Bumgarner: cvs2svn, Berkeley DB, and Python Bindings | Subversion on Mac OS X
• scplugin.tigris.org - Finder integration plugin
• WebSVN: Web interface for Subversion

I’ll update with more resources as I come across them, and with status/success reports, and if/how it integrates with XCode 1.5.

UPDATE: The install on the server went VERY well, thanks to Wilfredo Sanchez’ installers. The only thing that would have made it easier would have been a multi-package installer, for a single double-click installer for all packages. But that’s just gravy… The only “snag” I hit was on permissions in the /usr/local/apache/ directories - they appear to be owned by root out of the box, so other users (www, my account, whatever) can’t write to them (for config, or for log output…) Easy to switch the permissions (or, to run apache2 as root :-O )

I’ve just imported the whole APOLLO source tree into Subversion on the server, and am now checking it out again to test integration with XCode 1.5 (and with the Finder thanks to scplugin).

Hmm… svn appears to have choked on a .zip file on checkout… Might have to try checkout again… (later - that worked. weird)

UPDATE: It’s done, and running perfectly! Had some issues with installing the “wrong” client binaries - the one from tigris.org works best - and making sure XCode had the proper path to svn (if it’s got the wrong path, it appears to barf rather violently).

Looks like Subversion will be really nice to work with - easy to navigate packages via a web browser, and copy/paste the path needed for a very specific checkout. Now to get some actual work done…

UPDATE: Added link to websvn.tigris.org - after successful install on our server.

I just installed a local copy of the W3C HTML Validator tool on my laptop, thanks to the instructions provided by Apple. That was one heck of a process. Time in CVS checking stuff out, time in CPAN, time compiling stuff, finking stuff. All told, it took about an hour and a half (partially due to my slow internet connection at home at the moment).

Really appreciating the checkbox simplicity of the stuff that ships with MacOSX - I wonder if they’ll ship the validator on Tiger Server?

The guys at CodingMonkeys have just announced the release of SubEthaEdit 2.0

It looks basically the same (after a 30-second tryout), but has code completion, and the ability to invite folks to a shared document.

Looks like a good release (more info here: SubEthaEdit - Features), but it’s got a new network protocol which isn’t compatible with 1.0 - so everyone has to upgrade. So, go upgrade!

I’ve been using JEdit for a while now, and am constantly amazed at how complete it is. It’s even got a plug-in to manage XSLT transformations… Not as elegant as I’d usually like, but the integration into a kick-ass editor more than makes up for it.

WIth the addition of the Project Manager plugin, it’s pretty full-featured, and the somewhat sluggish Java UI is still very usable (even on a pokey TiBook 400! (one aside on the Project Manager plugin - it seems to require Java 1.4.1 to install, but if you run JEdit once under the 1.4.1 prerelease, you can install the plugin and it still works under 1.3.1…

I’ll retire Optimus Prime (and TestXSLT) for now and focus on JEdit and XSLT (which uses Xalan-J etc…) since it provides some rapid turnaround between editing XML, XSL and viewing output. I’ve set it to generate output.html in ~/Sites/ so I can bookmark it in Safari and reload as needed.

← Previous Page