Hi, With all this talk about different scm's. I have been using darcs (darcs.net) and I use it for a number of projects. Basically darcs is a distributed similar to bzr or git. I find that it works well, and has a number of features that I like, such as patch picking (means you can select which patches you take) and when you are recording a change set you can pick what changes are going to be included into the patch. Using tailor I have gone one step further and I have set up a darcs drupal repository which people can download from. To get the cvs version of drupal you can execute the following command. darcs get --partial http://repos.heydon.com.au/drupal this will get the latest version of the drupal repository. I have set it up so this repository will be synced with the drupal cvs repository every 6 hours. To update you local repository you just do the following in the drupal directory darcs pull -a and it will download all the new patches that have been applied. When you have made changes to your copy of drupal you can then do a darcs whatsnew and it will show you all the changes, and to record these use the following darcs record and you can then choose which changes will be included in the patch. I also have the web frontend going which can be gotten to at the following. http://repos.heydon.com.au/darcsweb/darcsweb.cgi?r=drupal;a=summary which is a little ugly at the moment as tailor doesn't really look that nice. There is also some problem ATM with the web frontend, but I think this is because of the version of python or something that dreamhost has done to python. Let me know what you think. Gordon.
Hi, One other things that I feel is important which darcs and other distributed scm tools do is that the author of the patch gets directly credited, even if they do not have write access to the main repository. So instead of Dries says patch x by y they will be credited directly. Gordon. On Fri, 2005-11-18 at 10:48 +1100, Gordon Heydon wrote:
Hi,
With all this talk about different scm's. I have been using darcs (darcs.net) and I use it for a number of projects.
Basically darcs is a distributed similar to bzr or git. I find that it works well, and has a number of features that I like, such as patch picking (means you can select which patches you take) and when you are recording a change set you can pick what changes are going to be included into the patch.
Using tailor I have gone one step further and I have set up a darcs drupal repository which people can download from. To get the cvs version of drupal you can execute the following command.
darcs get --partial http://repos.heydon.com.au/drupal
this will get the latest version of the drupal repository.
I have set it up so this repository will be synced with the drupal cvs repository every 6 hours.
To update you local repository you just do the following in the drupal directory
darcs pull -a
and it will download all the new patches that have been applied.
When you have made changes to your copy of drupal you can then do a
darcs whatsnew
and it will show you all the changes, and to record these use the following
darcs record
and you can then choose which changes will be included in the patch.
I also have the web frontend going which can be gotten to at the following.
http://repos.heydon.com.au/darcsweb/darcsweb.cgi?r=drupal;a=summary
which is a little ugly at the moment as tailor doesn't really look that nice. There is also some problem ATM with the web frontend, but I think this is because of the version of python or something that dreamhost has done to python.
Let me know what you think. Gordon.
!DSPAM:437d2078323347020818619!
Gordon, I love Darcs, unfortunately had no chance to test it in a larger developer environment yet. But in any case: darcs was designed *exactly* for developer communities and workflows like Drupal has. Not like svn that noly fixes the mayor annoyences of an ancient RCS. Darcs has no frontends, but who cares :) zwe dont even ship with an install frontend, so should we care about developer frontends? Thank you, Gordon for getting this going! Ber Op vrijdag 18 november 2005 00:48, schreef Gordon Heydon:
Hi,
With all this talk about different scm's. I have been using darcs (darcs.net) and I use it for a number of projects.
Basically darcs is a distributed similar to bzr or git. I find that it works well, and has a number of features that I like, such as patch picking (means you can select which patches you take) and when you are recording a change set you can pick what changes are going to be included into the patch.
Using tailor I have gone one step further and I have set up a darcs drupal repository which people can download from. To get the cvs version of drupal you can execute the following command.
darcs get --partial http://repos.heydon.com.au/drupal
this will get the latest version of the drupal repository.
I have set it up so this repository will be synced with the drupal cvs repository every 6 hours.
To update you local repository you just do the following in the drupal directory
darcs pull -a
and it will download all the new patches that have been applied.
When you have made changes to your copy of drupal you can then do a
darcs whatsnew
and it will show you all the changes, and to record these use the following
darcs record
and you can then choose which changes will be included in the patch.
I also have the web frontend going which can be gotten to at the following.
http://repos.heydon.com.au/darcsweb/darcsweb.cgi?r=drupal;a=summary
which is a little ugly at the moment as tailor doesn't really look that nice. There is also some problem ATM with the web frontend, but I think this is because of the version of python or something that dreamhost has done to python.
Let me know what you think. Gordon. Bèr -- [ Bèr Kessels | Drupal services www.webschuur.com ]
Ber You mean it has no GUI? I guess that is not a major setback. The people used to Tortoise CVS, WinCVS or Eclipse will see that now they have to write commands and options though ... Maybe it is worth a poll (what repository software do you use for drupal development?)
But in any case: darcs was designed *exactly* for developer communities and workflows like Drupal has. Not like svn that noly fixes the mayor annoyences of an ancient RCS. Darcs has no frontends, but who cares :) zwe dont even ship with an install frontend, so should we care about developer frontends?
Maybe it is worth a poll (what repository software do you use for drupal development?)
Let's not launch polls for the sake of launching polls. I'm not convinced it is useful to open up this discussion to the Drupal community at large. -- Dries Buytaert :: http://www.buytaert.net/
On 11/18/05, Dries Buytaert <dries.buytaert@gmail.com> wrote:
Maybe it is worth a poll (what repository software do you use for drupal development?)
Let's not launch polls for the sake of launching polls. I'm not convinced it is useful to open up this discussion to the Drupal community at large.
Agreed. Perhaps within the development list only?
Op vrijdag 18 november 2005 15:30, schreef Khalid B:
You mean it has no GUI?
I guess that is not a major setback. The people used to Tortoise CVS, WinCVS or Eclipse will see that now they have to write commands and options though ...
Neither do I. CVS (and SVN) are in essense so complex that they need GUI tools to help folks around. I beleive that darcs is so easy to learn (anyone can copy paste some commands, not?) that it needs no GUI. But then again, I am used to the commandline. click-kiddies might not agree. Bèr -- [ Bèr Kessels | Drupal services www.webschuur.com ]
Op vrijdag 18 november 2005 15:30, schreef Khalid B:
You mean it has no GUI?
I guess that is not a major setback. The people used to Tortoise CVS, WinCVS or Eclipse will see that now they have to write commands and options though ...
Neither do I. CVS (and SVN) are in essense so complex that they need GUI tools to help folks around.
I beleive that darcs is so easy to learn (anyone can copy paste some commands, not?) that it needs no GUI. But then again, I am used to the commandline. click-kiddies might not agree.
Being a *nix guy I use the command line version of CVS or SVN anyway. I find it easier than the GUIs. :-) I am in the minority, however, and I know that. Another point in SVN's favor is that it's conceptually the same as CVS. Any brain-space our current developers have devoted to the CVS modus operandi will translate to SVN very easily. I don't know that you can say the same for any of the distributed managers. That applies to new developers, too. Some random would-be developer who wants to get started is far far more likely to know, understand, and already have installed CVS or SVN than darcs, git, or whatever. That should be a consideration, too. --Larry Garfield
Hi, On Fri, 2005-11-18 at 09:58 +0100, Bèr Kessels wrote:
Gordon,
I love Darcs, unfortunately had no chance to test it in a larger developer environment yet.
But in any case: darcs was designed *exactly* for developer communities and workflows like Drupal has. Not like svn that noly fixes the mayor annoyences of an ancient RCS. Darcs has no frontends, but who cares :) zwe dont even ship with an install frontend, so should we care about developer frontends?
Even though it doesn't have any gui front ends the commands are very easy, and could be used by just about any developer.
Thank you, Gordon for getting this going!
I am glad it is appreciated. Gordon.
participants (5)
-
Bèr Kessels -
Dries Buytaert -
Gordon Heydon -
Khalid B -
larry＠garfieldtech.com