Subversion and SourceForge.net

Is it just me, or sf.net has decided to take some radical steps:

milanb@kiklop:~/devel/flamerobin-trunk$ svn up
svn: This client is too old to work with working copy 'flamerobin';
please get a newer Subversion client

milanb@kiklop:~/devel/flamerobin-trunk$ svn --version
svn, version 1.4.6 (r28521)
compiled Feb 1 2008, 17:17:53

I find it funny that you cannot use a less-than-2-years-old client to
access the server. I don't blame sf.net much though, I just hate
people who break backward compatibility (SVN team in this case).

Filed under  //   backward-compatibility   sourceforge   subversion  

Comments [0]

Yahoo Messenger

I really hate companies that simply don't care about backward
compatibilty. Yahoo! is phasing out it's Messenger while completely
disregarding the Linux users. It even offers me to download the new
version and then gives .exe file. Not that Linux port of Yahoo!
Messenger was really good, I'm using Kopete and Gaim/Pidgin. But
getting constant messages that "You are using an older version of
Yahoo! Messenger that is no longer supported." is a major PITA. Ok, I
got it the first time, but it keeps nagging.
 
This is getting to the point that I really don't care anymore. I guess
I'll switch to google talk or whatever. Maybe the new messenger is
sooo much better, and it will attract more new users they they lose.

Filed under  //   backward-compatibility   yahoo  

Comments [0]

32bit compatibility layer for 64bit Slackware

I'm currently using Slamd64 which has this built in, so I have yet to try it. I hope it's of good quality and Pat decides to include it in official package

32bit compatibility layer for 64bit Slackware

ftp://anorien.warwick.ac.uk/slamd64/slackware64-current/

Filed under  //   64bit   backward-compatibility   slackware  

Comments [0]

About