On Sun, 18 Oct 2015 16:05:14 +0200
Christian Kampka <christian_at_kampka.net> wrote:
> Glock is a command-line tool to lock dependencies to specific revisions,
> using a version control hook to keep those revisions in sync across a team.
> testing/glock/APKBUILD | 67 ++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 67 insertions(+)
> create mode 100644 testing/glock/APKBUILD
I used the snapshot function and uploaded the tarball.
However, the tarball I get must be different from the one you get.
>>> glock: Checking sha512sums...
sha512sum: WARNING: 1 of 1 computed checksums did NOT match
Because the remote file above failed the sha512sum check it will be deleted.
Rebuilding will cause it to re-download which in some cases may fix the problem.
>>> ERROR: glock: all failed
I suspect that go pulls in whatever happens to the latest git at that
point of some dependency.
Also, they have not made any releases, which indicates that 1) program
is not ready for packaging, 2) program is not supposed to be packaged.
I am open for suggestions how do properly package Go applications.
Did anyone bring up this for Go community? I have the impression that
go developers wants you to use the Go package manager.
Maybe we should just let the alpine linux users do that?
Received on Wed Nov 04 2015 - 09:13:45 GMT