Hi people! My boss ask me about a ruby library that can provide checking-out, updating and management code-bases from SVN's repositories. Wich is the better way to get access and manipulate code-bases from SVN's repositories using ruby? Is there any library can provide me these functionality? Can i use CUI's (Command User Interface) SVN through Ruby to do that? I just need a little light... Thank you.
on 2009-04-28 14:57
on 2009-04-28 15:19
On 28 avr. 09, at 08:57, Andrey R-andrey wrote: > Can i use CUI's (Command User Interface) SVN through Ruby to do that? > > I just need a little light... > > Thank you. > -- > Posted via http://www.ruby-forum.com/. > The first question I'd ask is why svn in this day and age? You might consider svn an evolutionary dead end. I don't know of a ruby svn library although one might exist. You could just call the command line functions. There happens to be a ruby implementation of git here: http://github.com/schacon/ruby-git/tree/master. That might be a better solution assuming you didn't have to use svn.
on 2009-04-28 21:37
Andrey R-andrey wrote: > My boss ask me about a ruby library that can provide checking-out, > updating and management code-bases from SVN's repositories. Wich is the > better way to get access and manipulate code-bases from SVN's > repositories using ruby? Invoking the command-line svn client from ruby is a reasonable approach. Have a look at the source for Capistrano, which does that. I'm also pretty sure there's a native ruby binding (or at least a SWIG binding) as part of libsvn. Google "svn ruby binding" or "libsvn ruby binding" That gives you a very low level guts interface, and last time I looked it wasn't very well documented, but there are examples out there if you search for them.
on 2009-04-28 21:52
On 28 avr. 09, at 15:37, Brian Candler wrote: > > Posted via http://www.ruby-forum.com/. > Invoking the command line is reasonable depending on how much efficiency you need. In most instances the time to call the command line function is going to be trivial. That isn't always the case. The Github folks found that it was too slow. So they ended up re- implementing git with Ruby. My guess is that in your case it doesn't matter. But I don't know enough about your project to say for sure.
on 2009-04-28 22:41
Juan Zanos wrote: > Invoking the command line is reasonable depending on how much > efficiency you need. And as usual - benchmark before making any premature decisions about performance. svn itself is not fast, especially when accessing a remote repository, so the overhead of invoking an external program is likely to be small in the overall scheme of things. That is, unless you're thinking of writing "svnhub" and having millions of users checking into your repositories :-)
on 2009-05-20 21:47
Did anyone ever get comfortable with any interface to Subversion from Ruby? I'm seeing a lot of stuff lying around, and I wonder how good it is. My interest has to do with secure authentication: When I pass an svn --username me --password mine cat http://h/repo/mfile it of course ends up on the process list. If I could use a ruby interface that can allow me to run everything with individual authentication and keeps it all off the process list and other public areas, I would be better off. This is not a real big deal otherwise, but if I can do it for auth, it would be worth migrating.
on 2009-05-20 22:00
Xeno Campanoli wrote: > Did anyone ever get comfortable with any interface to Subversion from > Ruby? I just came across detailled info on installing the ruby subversion bindings here: http://warehouseapp.com/installing/ruby-subversion-bindings warehouseapp itself is now open source, so you can look through it and see how they use it.
on 2009-05-21 02:02
Brian Candler wrote: > Xeno Campanoli wrote: >> Did anyone ever get comfortable with any interface to Subversion from >> Ruby? > > I just came across detailled info on installing the ruby subversion > bindings here: > http://warehouseapp.com/installing/ruby-subversion-bindings > > warehouseapp itself is now open source, so you can look through it and > see how they use it. Thank you. That looks helpful.