Source Control Management

I'd like to see some form of revision control tools for scripting become part of the client.

Preferably I'd like to be able to interface the client with my Subversion repository, but even basic CVS functionality would be great.

It gets to be something of a headache when working with three or more people on a project and having to go around asking who has the latest code revision.

While its possible to use revision control outside of SL via cutting and pasting into an external editor, it would be downright neat if we could perform checkout/commit operations directly from the inventory interface.

Good idea. It'd be nice if there was a way for LL to open up the in client script editing tools so we could modify it ourselves. Then we could add in subversion/cvs, function autocompletion, search/search and replace, etc.

The whole client doesn't need to be Open Source, but it would be nice to have a few pieces open where the community could do a bang up job.

Why not just start using SourceForge for you LSL scripts?

Actually, I was thinking about putting together an in-world version control system. It would track not just scripts, but objects, notecards, etc...

I have some of the design worked out. It would keep track of all the associated objects that are part of a package. It would allow you to make revision snapshots that were stored away. You could review version histories and retrieve any prior version.

Alas - it wouldn't be able to diff, but it could easily provide you with any two versions of a script for you to diff on your own.

Anyone beside me interested in this? Would it be useful? If I built it would you use it?

The original author recognizes there are cut & paste solutions. But he was commenting that it would be nice if there were a better way. Also SF is still opensource only, correct?



This is a neat idea. If you could do version control for objects, I think a lot of people would make use of it. I fear for the asset server

I think that's a great idea!
Rather than asking LL to put versioning in, let's ask them for the LSL functions we would need to enable scripters to buld their own. This would open up a new market, and allow residents to choose between different available version control systems to find one that suits their particular needs.

Let me clarify here.

I'm not asking for LL to host anything here, nor am I asking for some kind of LSL-based solution. What I'm asking for is for there to be someplace to put in a http:// or svn:// type url that can then be directly accessed from the inventory panel to perform checkout/commit operations, along with maybe a simple unified diff function to resolve conflicts. This would only apply to scripts.

The problem with trying to cook up a solution that uses lsl is that lsl is inherently prim-based; the instant you start involving prims, you start running up aginst the inflexibility of the permissions system. Then there's the whole matter of reinventing the wheel.