Re: Wrong link not pointing to the release tarball

From: Pavel Raiskup <praiskup(at)redhat(dot)com>
To: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>
Cc: Dave Cramer <pg(at)fastcrypt(dot)com>, List <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Wrong link not pointing to the release tarball
Date: 2016-01-22 13:53:17
Message-ID: 2794409.PzZyu5Xvg8@nb.usersys.redhat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

On Friday 22 of January 2016 16:47:15 Vladimir Sitnikov wrote:
> In fact, there are two types of "source artifacts":
> 1) source.jar -- this one is for IDE integration and manual
> inspection. It is not suitable for a build process.
> 2) *.tar.gz -- I've no idea why is it useful, however, it existed
> before mavenization, thus it still exists.

Thanks, good to hear!

> I've no idea *.tar.gz artifact is suitable for build purposes.

It definitely is suitable, that helps us to build jar file from source --
from beginning.

> Dave, I think Pavel is right in a sense that (Source, 9.4 Build 1207)
> link points to postgresql-9.4.1207-sources.jar while it should point
> to postgresql-9.4.1207-dist.tar.gz (like the previous versions).

If you could fix the link, that would make our life easier then. I was
not able to find the link.

> Dave>The recommended way to build is to pull from github.
>
> That is true. "build from github tarball" is tested better (it is used
> for driver releases) than "build from *.tar.gz" (it is write-only).

Well, tarball got by `git archive` would be good enough, too. But with
that we are not completely sure that the particular commit ID matches
exactly the version you released in pre-built binaries.

Thanks, Pavel

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Vitalii Tymchyshyn 2016-01-22 14:03:50 Re: Wrong link not pointing to the release tarball
Previous Message Pavel Raiskup 2016-01-22 13:47:19 Re: Wrong link not pointing to the release tarball