I’m glad to hear it only took you half an hour to write the script, but again, its way overkill to have to follow any kind of build or deployment process whatsoever for these scripts.
Thanks all for the helpful feedback, I will try to find a solution outside of fossil. > On Aug 15, 2017, at 3:37 PM, Warren Young <war...@etr-usa.com> wrote: > > On Aug 15, 2017, at 3:07 PM, Steve Schow <st...@bstage.com> wrote: >> >> yea that’s way overkill. > > The attached script creates versioned zip files given a Fossil-versioned file > name containing the file and a manifest file called VERSION. You can > therefore get the version number in the file name and in the VERSION file. > > Time to develop: under half an hour, including testing. > >> Creating deployment steps for each and every one of them is not a practical >> solution. > > The attached script is a wrapper for zip(1). Unless “deployment” means “copy > file directly out of Fossil into the production tree” you needed something > like this anyway. > > > <ship>_______________________________________________ > 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
