Thanks Warren. I’m pretty handy with sed and awk and all the rest. I’m just trying to figure out the best way to work out an automatic workflow for having a version in the source comment.
wrapper scripts around fossil that do this sort of thing might work, but see if each script file has its own independent version, its not part of a greater whole per say…its just the version of that exact file..nothing more……appearing in the source comment. Honestly, its probably just easier to remember to manually update it before committing and never forget, but I hate manual anything. having a seperate script that brings something in from another file is always a possibility but if every file has its own verison…then what…a seperate version file for every js file? starts to get kind of ridiculous… > On Aug 15, 2017, at 3:52 PM, Warren Young <war...@etr-usa.com> wrote: > > On Aug 15, 2017, at 3:50 PM, Steve Schow <st...@bstage.com> wrote: >> >> I will try to find a solution outside of fossil. > > The ship script gets you 95% of the way there. > > For example, if you absolutely positively had to have the version number > embedded into the deployed JS file, you could substitute it into the shipped > JS file with a few lines of modifications to my script. > > Basically, swap the zip call for a call to sed. > _______________________________________________ > 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
