[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: If anyone is considering upgrading their development machine to OSX 10.9 ...

From: Ben Reser <ben_at_reser.org>
Date: Sat, 25 Jan 2014 23:00:05 -0800

On 1/25/14, 8:59 PM, Branko Čibej wrote:
> That was the first thing I tried, but the latest XCode doesn't offer that
> option any longer on Mavericks.
> Hmm ... they can apparently be downloaded separately. Let me try that ...

I've moved all my machines to 10.9 a few weeks back. I had a VM in Parallels
up for some testing before that.

You need to run this from the terminal after installing XCode:
xcode-select --install

Here are the things I've noticed about 10.9 that annoyed the hell out of me.

gdb is gone. I've been shifting my debugging to lldb anyway but there is one
giant gaping hole in lldb support that has me going back to gdb. lldb has no
functionality for following forks. So if you need to debug something that
forks, it's like going back to the dark ages when you had to set breakpoints on
the fork and then catch the next process with a separate debugger.

The other thing I've noticed is Apple has decided not to ship the Python
bindings for Subversion anymore. Nor are they shipping the Ruby bindings.
They are however still shipping the Perl bindings. Ruby I can kind of
understand since they're shipping Ruby 2.0.0 and we didn't even have Ruby 1.8
support until 1.8.0 and they're of course shipping 1.7.10. Python I don't get
since they're still shipping Python 2.7.5. Since they're shipping git and
git-svn I'd imagine that's the only reason that Perl hasn't been yanked. This
has made life difficult for Mercurial people because Mercurial was using our
Python bindings for interoperability. I wouldn't have noticed this if
which-error.py didn't depend on the Python bindings, I don't usually bother to
install the bindings.
Received on 2014-01-26 08:00:52 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.