items from the mind of an idiot savant

not fit for print

Today’s tutorial went without a hitch. Everything worked as advertised. In fact it only took me about 35 minutes. Just follow the tutorial and you’re fine.

Don’t forget to commit your changes in to your Subversion repository.

Hey, wasn’t that interesting how you had to get the css files from their repository? Did you notice how when you went to get them, you went to a directory called “tags/release_day_3″? That’s kind of cool how you can tag a version like that. I did some searching around and read that sometimes people will name the tag directory “releases”. That makes a bit more sense to me in english rather than “tags”. Except I realized that you may want have tags that are not necessarily releases. I suggest using both. That way people can get released versions, unreleased tagged versions, and even the current version.

So how the hell do you make a tag?
Well if you’ve been doing any of the digging I’ve been doing, you probably stumbled across this site: http://svnbook.red-bean.com/. Here’s how to Create a Simple Tag. If your setup like I showed you earlier, you can just do $ svn copy file:///$SVNREP_DIR/askeet/trunk file:///$SVNREP_DIR/askeet/tags/day3 -m "Tagging day 3".

You may not have noticed, but on day 3 we did something a bit different. We deleted a file. OH MY GOD! That’s simple enough, what’s the big deal? When you delete a file, subversion doesn’t realize it. You need to let subversion know that file is no longer being used. There’s probably some command line command to issue here, but I’ve had enough of that, and I work on a mac, so I’d like something a bit prettier.

I looked at a few Subversion GUI apps. I’m almost hesitant to say I like this one because it seems like they may switch the license from free to pay sometime in the future, and I’
m way too cheap to pay for software. Of the four or five Subversion GUI apps I looked at, I liked iSVN. You can probably find others by searching for subversion on MacUpdate or VersionTracker.

Setting up iSVN was easy. All I had to do was point it to my local working copy of aseet! and it figured out the rest. So the first thing I did was click the Commit button. It told me that a lot of my files had not been committed. Maybe we did something wrong earlier, but now iSVN has come to our rescue. So I commit my changes and everything seems to be fine now.

I liked how the example tutorial has tags for each day. Maybe we should do the same. I showed you how to do it earlier from the command line, but not all my files were in the trunk properly, so I’m going to do it again using iSVN.

I just right click[That's ctrl+click for you one button mouse people. And for the love of god, buy a multi-button mouse.] on askeet, and select “Browse Repository…”. It shows you the Subversion repository instead of only your local copy. I deleted my day3 tag so I can make a new one. I selected the trunk directory and “Copy To…”. I set the target directory to the tags folder, and renamed it to “day3″. That was way more intuitive than some command line, and I can always check to make sure that I’m creating a tag that doesn’t already exist. I’ll probably use both iSVN and the command line. Feel free to use what your comfortable with.