On Fri, Mar 25, 2016 at 03:25:21PM +0100, Mark Rotteveel wrote:
> On 25-3-2016 10:59, Dmitry Yemanov wrote:
> >
> > We considered not storing buildno in the repo, but no good solution was
> > found.
> >
> > I don't want to pollute our build scripts with "check whether git is
> > installed and available in the path", "check whether sources contain
> > .git inside", etc. But without that, we cannot enforce outside builders
> > to generate the buildno properly. I don't care what code you build for
> > yourself, but for non-official snapshot builds and Linux ports this
> > becomes a problem. I don't want to scratch my head every time someone
> > says "I'm using FB v3.4.5.0 and it crashes."
> >
> > If you have some clever idea, I'm all ears.
>
> I suggested using tags for this. What is the problem with doing that?
When you export the sources for build, the information about tag is lost
so that you still don't see what commit does the tarball come from. If
the reporter knows the tarball was created from, say, tag v3.0.0.54321,
he can also know the commit id it was created from; but neither is an
information that would be automatically preserved on export.
On the other hand, passing the commit id can be easily automated for
official daily snapshots and users building Firebird themselves from the
repository could be taught to note and report the commit id used for
their builds - as they do in many other projects.
Michal Kubecek
------------------------------------------------------------------------------
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
