Re: darcs switchover
On 2005-12-19, Malcolm Wallace [EMAIL PROTECTED] wrote: Ross Paterson [EMAIL PROTECTED] writes: No problem for me if you switch over at any time. But how about having a separate repository for each library package? Seconded. Simon, any thoughts? We could go about this one of two ways: 1) Just make branches of the current libraries repo, and in each one, remove the files that aren't relevant for a particular package 2) Re-convert the CVS files from scratch I would prefer #1 by far ;-) -- John ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
Re: darcs switchover
On Tue, Dec 20, 2005 at 03:50:02PM +, John Goerzen wrote: On 2005-12-19, Malcolm Wallace [EMAIL PROTECTED] wrote: Ross Paterson [EMAIL PROTECTED] 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. ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
Re: darcs switchover
Simon Marlow [EMAIL PROTECTED] 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? Regards, Malcolm ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
darcs commit emails was Re: darcs switchover
Malcolm Wallace [EMAIL PROTECTED] 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. ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
Re: darcs switchover
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. John -- John Meacham - ⑆repetae.net⑆john⑈ ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
Re: darcs switchover
Malcolm.Wallace: Simon Marlow [EMAIL PROTECTED] 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 ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
Re: darcs switchover
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 ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
Re: darcs switchover
On Wed, Dec 21, 2005 at 10:56:14AM +1100, Donald Bruce Stewart wrote:
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.
the way darcs itself works is that everyone uses darcs send, even david
and his script picks up patches signed by him and automatically applies
them. In any case, having darcs send go to a public list is really nice.
another possibility if you don't want to mess with gpg is that everyone
darcs send's and then the patches are 'pushed' by a main developer off
the list (which sometimes might be their own patches). I have attached a
handy little script I have bound to 'A'pply in mutt which facilitates this.
John
--
John Meacham - ⑆repetae.net⑆john⑈
#!/usr/bin/perl -w
use strict;
my $m;
my $r;
while () {
/^DarcsURL\:\s+http\:\/\/.*\/repos\/(\w+)/ and $r = $1;
$m .= $_;
}
die Could not find repo name. unless $r;
print Darcs Repo: $r\n;
umask 0022;
open FOO, | darcs apply --verbose --no-test --repodir ~/repos/$r or die
Could not pipe to darcs;
print FOO $m\n;
close FOO;
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
