[darcs-users] proposal for 'darcs init' flags (was: Re: Patches are immu)

David Roundy droundy at abridgegame.org
Tue Oct 26 11:28:49 UTC 2004


On Mon, Oct 25, 2004 at 11:15:20PM +0000, Mark Stosberg wrote:
> On 2004-10-25, Ketil Malde <ketil at ii.uib.no> wrote:
> > anselmg at t-online.de (Anselm R. Garbe) writes:
> >
> >> Allow rerecord only for the last (most recent) patch (and only
> >> that patch!) until:
> >
> >> i)   it has _not_ been pulled from some client or
> >
> > I think the problem is that darcs doesn't know this - you can pull
> > with just read access.  One possible solution (re the
> > working/distribution repo distinction) could be to prohibit pull from
> > working repos (and prohibit rerecord etc in distribution repos) -
> > although I think it is sometimes useful to pull between working repos
> > as well.

It definitely *is* useful to pull between working repos.

> Perhaps this whole situation would be a good reason to add the first
> option flag to "initialize":
> 
>    'working' and 'archive'. If 'archive' is selected, the following
>    commands will be disabled, since they are a bad idea to use on
>    archives (XXX list commands here). 'working' is the default and is
>    how darcs has worked historically-- all commands are enabled.  
> 
> There other ways to express the same idea. You could have:
>
> --archive
> --not-archive
> 
> As you might guess, all these would do is initialize the prefs file
> with those command. They could be adjusted to suit later. 

I like this idea.  Perhaps something like --public, --private and
--working? I'm not sure I care for archive as a name.  --private would only
be implemented if we had a flag that kept others from pulling from us.
-- 
David Roundy
http://www.abridgegame.org




More information about the darcs-users mailing list