On Dec 27, 2017, at 4:42 PM, Warren Young <war...@etr-usa.com> wrote: > > What it’s going to give you is a short prefix of the Fossil checkin ID
On reading the script, it depends on being installed in a directory one level below the checkout root. I have it in a “tools” subdirectory of that particular repository, where I place all non-installed scripts and helper executables, but the depth is all it really cares about. If you place it somewhere else, you might change all the references to “tools/“. If you place it deeper than one level or outside the repository, you’ll also have to adjust the path manipulation code. It depends on that project’s release version tagging scheme, done by tools/mkrel, which you might also find interesting. Release version tags in this project are of the form “v20171227”: if you run this script on a checkout so tagged, you get that tag as output, which you can use anywhere in Fossil that you could use a checkin ID. If you run it anywhere else in the repository, it gives you a string like “id[abcde12345]”, which makes it easy to visually distinguish from a version tag. The “else” clause tries to deal with the case of building from a source tarball, but it’s only capable of coping with our release tarball naming scheme. If nothing else, this script should give you some ideas for replacing it with something you find more useful. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
