I know, I know: real men use the commandline. But it's the 21st century and I'd like to be able to click on things when I interact with them (if not, you know, use a magic iThreeFingerSwipe gesture on a touchscreen). The thing is that whenever I try to do any kind of administration of svn (creating a repo, adding to it, checking out--anything but the simplest of update/commit cycles), I go through about four or five different errors before it works out. I'm not terrible at bash, but there's something about svn that doesn't agree with what I think is intuitive, that makes the process more painful that it has to be, and that makes me have that special kind of worrying that comes from feeling like I'm working with something fragile and like I need to back everything up to external media just to make sure I don't lose anything.
So I'd like a client. But they all suffer from even more problems. Why does WebSVN, a php-based web client, somehow rely on a specific (and presently outdated--27/02/2010) version of svn, instead of just the one local to the server? Why does RapidSVN give me
"Error: Error while updating filelist (Unknown error!
In file subversion/libsvn_ra_svn/streams.c Line 75)"
when it's supposed to make thinks better?
For now, at least when it comes to my digital life/homework and not major code projects, I'll stick to the OS's gui and just not deleting things, I think.
Saturday, February 27, 2010
Subscribe to:
Posts (Atom)
