On 2006-03-20, Juliusz Chroboczek <[EMAIL PROTECTED]> wrote:
>> prehooks. I think that most needs for RCS style keywords could be
>> dealt with using a perl script, that just does a really simple regexp
>> check for keywords and replaces them.
>
> If you do that, you're going to get some really nasty recursive
> conflicts whenever you try to do any merges. (That's a symptom of the
> fact that RCS-style keywords just don't work with Darcs' model.)
>
> I think the only solution would be to have your script run at predist
> time, so that the substituted keywords don't get into the repository
> itself.
I switched from CVS too, and also missed the 'keyword' functionality,
but only briefly. Now having used darcs for over a year, I don't miss it
at all.
In fact, lately keywords have annoyed me.
- Sometimes keywords change when the files don't. I think this can
happen with files on a branch, or if the format of the keyword line
itself changes. When tracking a CVS project with darcs, it makes a
bunch of the files falsely appear to have a "difference" when they
don't, except for that line.
'diff' tools would also report a difference when there might be none.
I like Juliusz' idea of running a script at predist time, although
personally I get by fine without any keywords at all anymore.
Mark
--
http://mark.stosberg.com/
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
