On Tue, Aug 15, 2017 at 8:09 PM, Steve Schow <st...@bstage.com> wrote:
> well I’m hoping to have a version that is stamped into the comments of the > actual file as well. Stamping that version would change the hash. To the best of my knowledge that feature cannot be implemented with DVCS (which requires hashing (non-serial IDs) for versioning). > 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. For those types of things you've got to "build" a version of those scripts, injecting the current version 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. But RCS was missing about 99% of the features of a modern DVCS (and RCS didn't have the "D" at all). > 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? > Right. But the moment you do that, you change the hashes of those files, making them completely different content as far as any DVCS is concerned. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
