The latest debate over whether the 'rm' and 'mv' commands--in the fossil shell--should behave exactly line the 'rm' and 'mv' commands--in the various OS command shells--proves one thing unequivocally:
Fossil is an piece of software that can spark vehement opinions from its users. Fossil matters. "Holy wars" are tedious, but they do prove that the (primary) subject of the battles is *something that matters*, and that should make the Fossil developers proud. Aside from that, here's an enhancement suggestion for "when there's time": A little self-knowledge can be A Good Thing. Maybe Fossil could keep a list of behavior and db format changes in each repository? I'm thinking it could be an event artifact. The overhead ought to be small. It could keep a list of messages, and Fossil's behavior would be extended to trigger displaying the message when a changed command is attempted, instead of executing the command. Scripts running Fossil would log the error (or so one would hope!) Once the user acknowledged the changed command (fossil set ok foo) the command would run, and the warning would stop appearing. Finally, if there are command changes in a new version, a "Some commands have changed, see help" message could fire when fossil is invoked, until they've all been acknowledged. The user could downgrade until they fix scripts, etc. It would catch users that haven't grabbed a zip or "pull"ed in a long time. I don't see how anybody could get surprised, or lose data from a changed command. Ok, maybe a _little_ surprised, but not in an horribly unpleasant way. Lots of work, but it would be a sort of "meta-solution" to all of this. --kkinnell (using host megagate under the commercial root-domain) _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
