Am Freitag, 16. Dezember 2005 12:20 schrieb Malcolm Wallace:

I've been looking at the cvs configuration file CVSROOT/modules. I /think/ the procedure is something like changing this:

nhc98src -d nhc98 nhc98 nhc98libraries -d nhc98/src/libraries fptools/libraries nhc98 -a nhc98src nhc98libraries

to this:

nhc98src -d nhc98 nhc98 nhc98libraries -o darcs get --reponame=nhc98/src/libraries \ http://cvs.haskell.org/darcs/libraries nhc98 -a nhc98src nhc98libraries

and then a fresh cvs checkout of the nhc98 would be required in order to pick up the new location. Has anyone else tried this kind of tweak before and confirm that it is likely to work? If not, I might test it out with the smaller cpphs module initially.

As already mentioned on the cvs-all list this morning, this does not work... :-( Cheers, S.

Ross Paterson writes:

No problem for me if you switch over at any time. But how about having a separate repository for each library package?

Seconded. Regards, Malcolm

On Tue, Dec 20, 2005 at 03:50:02PM +0000, John Goerzen wrote:

On 2005-12-19, Malcolm Wallace wrote:

...

Ross Paterson writes:

...

But how about having a separate repository for each library package?

Seconded.

Simon, any thoughts?

Also, if the library packages are separate, the rest of the stuff in the libraries directory would be part of GHC's build system (nhc98 too at the moment, but it sounds like Malcolm will be changing that) so might as well be part of the ghc repository.

Malcolm Wallace writes:

One thing it occurs to me to ask is what will be happening to CVS commit messages, once the switchover to darcs happens?

rss2email is one solution. It's a python script that runs from cron, so you won't have to worry about fiddling with darcs posthooks or anything. -- Shae Matijs Erisson - http://www.ScannedInAvian.com/ - Sockmonster once said: You could switch out the unicycles for badgers, and the game would be the same.

john:

can't we just make 'darcs send' send the patches to a public list so people can see them that way as they are sent in.

I think the problem would be that we still want multiple developers to darcs push over ssh, don't we? Rather than darcs sending patches to a list, for a mainatiner to pick up. -- Don

Malcolm.Wallace:

"Simon Marlow" writes:

...

The aim is to eventually switch over to using darcs for our revision control. The point of this message is to find out what constraints people have that will affect when we can throw the switch.

One thing it occurs to me to ask is what will be happening to CVS commit messages, once the switchover to darcs happens?

I have investigated this briefly, and it seems that darcs does not yet directly support mailing out commit messages from a repository. There is a wrapper script at darcs get http://www.cse.unsw.edu.au/~dons/code/darcs-mail but this requires administration privileges on the hosting machine, since you need to rename the darcs binary proper, then install the wrapper in its place. Also, it is unclear to me whether this wrapper works equally well in all situations, e.g. with 'darcs apply' on the hosting machine, 'darcs push' from a separate repository on the same host, or 'darcs push' from a remote machine with ssh.

Anyone sufficiently familiar with this to shed any light?

darcs-mail mails changes summaries when `apply --all' is on the cmd line -- which is the case when pushing over ssh. So it works quite nicely for the situation where you push over ssh to a central repository. A nice summary is then sent out to each address in _darcs/prefs/mailinglist. We've used this internally at UNSW for about 6 months now, and has worked quite well. I originally wrote this script as a temporary fix until darcs supported post-apply hooks. If it does now, perhaps there's no need for the wrapper, and instead a mail program can be invoked by darcs itself as a hook (i.e. just the core of darcs-mail can be `hooked'). So, in summary, if darcs post-apply hooks now work, we could strip down darcs-mail for our purposes, otherwise we could use darcs-mail, (though it only works over darcs push ssh atm). -- Don

On 2005-12-21, Malcolm Wallace wrote:

Ah, yes I have just upgraded to darcs 1.05 (from 1.03), and there are posthooks available for every command now. However, there is

FWIW, it is not the posthook but the cc pref for apply that I'm looking at. You can set it so that apply itself generates a message when something is applied. -- John