On Sat, Dec 3, 2011 at 12:03 AM, Eric <e...@deptj.eu> wrote: > 1) needed at build or install time, in which case the build and install > scripts create them > > 2) part of my common development environment, in which case they are not > part of what I am developing and do not belong in its repository
It's not up to fossil to decide what goes into the repository (with some minor exceptions, e.g. certain characters aren't allowed in filenames for portability reasons). Some devs enjoy checking in files matching both conditions (1) and (2). e.g. not all platforms support real build scripts (Windows), in which case adding them to the repo might be a project requirement. e.g. fossil's own makefiles are script-generated, but checked in to the repo nonetheless for build portability reasons. On a similar note, i personally find it "absolutely insane" to manage 200MB binary files via source control, but that doesn't invalidate some peoples' need/desire to do so. -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
