On Mon, 2 Jul 2012 08:08:18 -0400 Richard Hipp <d...@sqlite.org> wrote:
> I am willing to *consider* some option that says "do not commit these > files, even if they change, unless that are specifically named on the > command-line". I think this would be easy to implement by messing > with the is_selected()/if_selected() > function <http://www.fossil-scm.org/fossil/artifact/9b15f53f6?ln=1366-1385>. My issue with this solution is that this doesn't really solve the problem as I've encountered it. That is, a config file that needs local changes to run/build, but with a base version in the repo that needs evolves along with the project. My solution has been to push things out to the build system. What gets stored in the repo is config.template. In this, the "values" for everything document what they are used for. The end user (or a command run by them, depending) creates "config" from that, filling in the values as appropriate. The build (or launch, depending) system breaks if the local version doesn't exist, and issues a warning if the template is newer than the local copy (when it gets updated). A SCM system could do that, with a private branch of the config file for everyone who is building (running) the project, but that seems like overkill. <mike -- Mike Meyer <m...@mired.org> http://www.mired.org/ Independent Software developer/SCM consultant, email for more information. O< ascii ribbon campaign - stop html mail - www.asciiribbon.org _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
