On Friday 22 of January 2016 17:05:38 Vladimir Sitnikov wrote:
> Pavel> But with
> Pavel>that we are not completely sure that the particular commit ID matches
> Pavel>exactly the version you released in pre-built binaries.
>
> Technically speaking, maven creates a git tag (e.g. REL9.4.1207), then
> it checks out git tree of that particular commit ID (from github!) to a
> clean folder, then it builds the driver, then the results are published.
>
> As long as we use maven, release tag will point to the commit ID
> that is used for the release.
This sounds fine, the only bottleneck I can think of is that people among
distributions used to have "that" tarball (concrete name, structure, etc.)
and to switch from the (very) old version to the REL9.4.1208 they will
need to change a bit more things.
I'm OK to fix our spec file (build "declarative" "script") [1] to follow
new format, and those who have not raised their hands yet will need to do
it post-mortem. Could we fix the link coming from download.html to the
tarball -- to clearly say what source linux distribution should use?
> Our current *.tar.gz is closer to maven's "bin.tar.gz". In other words,
> our tar.gz is for the case when all artifacts like source jar, release jar,
> dependencies, etc, are required at once.
Might be, that bin.tar.gz is not known to me :(.
[1] http://pkgs.fedoraproject.org/cgit/rpms/postgresql-jdbc.git/tree/postgresql-jdbc.spec
Pavel