Another (perhaps simpler) way to do this is to use the package installers at http://www.collab.net/downloads/community/ instead. The binaries will be installed in /opt/subversion so they don't collide with the built-in SVN 1.4.4 tool set.
Alternatively, you can make Versions use SVN 1.4 internally by changing the preferences. You'll have to check out new working copies if you do this, though. And I personally prefer using newer versions of SVN anyway. Still, this is the least intrusive approach. - Quinn On Jan 4, 2010, at 8:41 AM, brian wrote: > I solved this by installing subversion 1.6.5 via http://www.macports.org/ > > On Jan 3, 8:22 am, Jean-Rubin L <jrleon...@gmail.com> wrote: >> Hi, >> I am using Versions but I'm using BBedit to edit my files. I'd like to >> commit from BBedit but when I try to do so it says the version of >> subversion is too old. Long story short, BBedit is using the default >> svn client sent with my leopard installation. To allow it to use a >> newer version I would like it to use 1.6.6 command line svn version >> that version itself uses but I cannot find the path for this. Also >> when I try to download and install your 1.5 installer, it fails saying >> there's a newer version of the files already installed. Is there a way >> I can point BBedit to the right version of svn command line. Can >> anyone tell me where these files are? >> >> I'm using Versions 1.07 on a PPC powerbook running leopard. >> Thanks, >> JR > > -- > > You received this message because you are subscribed to the Google Groups > "Versions" group. > To post to this group, send email to versi...@googlegroups.com. > To unsubscribe from this group, send email to > versions+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/versions?hl=en. > >
smime.p7s
Description: S/MIME cryptographic signature
