well I’m hoping to have a version that is stamped into the comments of the actual file as well. For example I have some javascripts that are used in another entirely closed environment that doesn’t have access to fossil, so it would be nice to be able to know which version of the script is being used…with many updates happening in early stages of development, its easy to forget to manually update a comment with a number. what I miss about RCS, is it would bump up the RCS number and could substitute that into the source for me during checkout. I guess since fossil doesn’t number versions that way…just uses hashes…there is no way to have fossil do that. Just wondering if anyone else has any other workflow suggestions for how to automatically embed a bumped up version number with each checkin into a comment of the source itself..
It sounds like what I would need to do is keep a seperate db that associates hashes with version numbers and then use a wrapper script or something to do this work of substituting that into the source comment. yes? > On Aug 15, 2017, at 12:03 PM, Richard Hipp <d...@sqlite.org> wrote: > > On 8/15/17, Steve Schow <st...@bstage.com> wrote: >> Related to this question, anyone have any workflow suggestions for >> accomplishing this aside from remembering to bump the number manually in the >> file before every important checkin or commit? > > Fossil is self-hosting on Fossil. The way it works is that there is a > "VERSION" file at the top-level that contains the current project > version number as text. This version number gets baked into the > binary by the makefile. We manually edit the "VERSION" file prior to > each release. > > https://www.fossil-scm.org/fossil/finfo?name=VERSION > > The "version number" of individual files is inherent in its SHA3 hash > (or SHA1 historically). If you have some file and you want to ask > "what check-in does this file go with" you can type: > > fossil whatis $HASHPREFIX > > And Fossil will tell you about that file - when it was first checked > in, etc. To compute a SHA3 hash on an unknown file: > > fossil sha3sum $FILENAME > > > -- > D. Richard Hipp > d...@sqlite.org > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
