25.03.2016 22:48, Adriano dos Santos Fernandes wrote: >> This gives us a buildno counted in days, not in commits (as now). > > In practive it's not different. > > Doesn't the script is running per day like was in svn? > > Right, that means the snapshot build has a "perfect" buildno, but the > people who download zip does not. > > With the solution above, we can make snapshot builds to checkout tree or > 00:00 hour of the given date, so it can have a perfect buildno that we > can convert to date as well.
Or we may adopt a combined solution. For our own builds, both official and snapshots, calculate the build number as commit count (as now, but without storing in the repo). For external builds, gather LAST_COMMIT and embed it into the version string *as date*. I.e. something like: Firebird-4.0.0.123-Unstable (official) vs Firebird-4.0.0.0-20160326-Unstable (unofficial) Port maintainers will either use our git-based scripts to get a proper build number or fix the version string themselves with whatever numbering they want. And for any non-official snapshots we will see them as obviously non-official and still be able to determine what code checkout they belong to. Does anyone think it looks better? Dmitry ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
