| Author |
Message |
BlazingPhoenix
Ree-Yees
Joined: 22 Mar 2008
|
 Posted: Jan 16, 2009 02:03 Post subject: SVN? |
    |
|
How about an SVN for DarkXL? Would this be a good idea or not? It could make bug finding a lot easier.
|
|
lucius
DarkXL Developer
Joined: 17 Feb 2008
|
|
Burning Gundam
Kell Dragon
Joined: 28 Sep 2003
|
| Posted: Jan 16, 2009 05:40 Post subject: |
|
|
I seem to notice you've answered this question in a variety of threads. Might I suggest making an "About DXL" Sticky in the forum? You could outline the basics and lay down some ground rules for yourself so people don't ask you the same questions over and over.
Just a thought. And it may already exist, I'm just too lazy at the moment to find it.
_________________
I don't think outside the box... I customize it. |
|
lucius
DarkXL Developer
Joined: 17 Feb 2008
|
|
Emon
Ree-Yees
Joined: 10 Aug 2007
|
| Posted: Jan 18, 2009 20:47 Post subject: |
|
|
SVN is old and busted. I would highly recommend Mercurial for source control. It's a distributed SCM like git, but better. It's more well supported on a variety of platforms. It has a great GUI client for windows, TortoiseHg, and a plugin for Visual Studio called VisualHg (which uses TortoiseHg as its backend).
|
|
lucius
DarkXL Developer
Joined: 17 Feb 2008
|
| Posted: Jan 18, 2009 21:25 Post subject: |
|
|
Emon wrote:
SVN is old and busted. I would highly recommend Mercurial for source control. It's a distributed SCM like git, but better. It's more well supported on a variety of platforms. It has a great GUI client for windows, TortoiseHg, and a plugin for Visual Studio called VisualHg (which uses TortoiseHg as its backend).
Thanks for the tip, I'll check it out at some point.
_________________
DarkXL....http://darkxl.wordpress.com |
|
Gez
Gamorrean
Joined: 05 May 2008
|
| Posted: Jan 18, 2009 22:15 Post subject: |
|
|
It seems to me a distributed CMS would go against lucius' desire to keep DarkXL somewhat centralized -- a system like that one encourages fragmentation.
More precisely, it's geared toward a project shared by multiple developers. A centralized system like SVN is still perfectly serviceable for a project with a lead developer and minor contributors.
|
|
Emon
Ree-Yees
Joined: 10 Aug 2007
|
| Posted: Jan 19, 2009 18:55 Post subject: |
|
|
Actually, distributed SCMs are great for small and personal projects because of the lack of overhead of configuration management. It's easy to work on your own repository then push the changes to a centralized one whenever you want. It's not accurate to say that it encourages fragmentation, rather that it allows wide distribution. You don't have to take advantage of such features if you don't want to.
The main reason I use Mercurial is not because it's distributed, but because the tools and IDE integration are better than SVN, at least for Visual Studio. AnkhSVN is a VS plugin that has been around for a long time, but it still has loads of problems. If these are problems with AnkhSVN, with SVN or both, I'm unsure, but Mercurial "just works."
|
|
|
Maybe a FAQ or something like that will be handy (even its a sticky post in the forum, linked to from the website).