Aaah ok, so my usage should have been v1.0.0-pre-release.1 and
v1.0.0-pre-release.2 ; and indeed,
when I've tested it it does work.
Thank you
On Wednesday, April 29, 2020 at 8:41:39 PM UTC, Sean Liao wrote:
>
> semver point 10:
> > Build metadata MUST be ignored when determining version
On Wednesday, April 29, 2020 at 6:57:55 PM UTC, Uli Kunitz wrote:
>
> The documentation provided by go help modules doesn't refer to semver.org
> and the Backus-Naur-Form there, so you cannot assume it is supported. The
> semver.org BNF doesn't support the leading v letter, so Go modules
>
On Wednesday, April 29, 2020 at 6:57:55 PM UTC, Uli Kunitz wrote:
>
> The documentation provided by go help modules doesn't refer to semver.org
> and the Backus-Naur-Form there, so you cannot assume it is supported. The
> semver.org BNF doesn't support the leading v letter, so Go modules
>
Hello,
recently I've created a new golang library and released it with pre-release
version first to catch any bugs before doing proper 1.0.0 release.
The pre-release version was called 1.0.0-pre-release+1 , which according
to https://semver.org/ should be completely legal semver. If I read the
On Sunday, January 5, 2020 at 11:02:52 AM UTC, Amnon Baron Cohen wrote:
> If you are happy publishing a zip archive rather than a tarball,
> then you can server the module download protocol directly.
> See https://research.swtch.com/vgo-module#download_protocol
That definitely looks interesting
Greetings,
I would like to ask if it is possible to publish go module using tarball and
later on somehow use it. All examples I was able are about using go modules
from some git repository. However, what I would like to do is publish
tarball
same way as I would do for C projects (`make dist`)
Hello,
while looking into how alpine linux builds golang I've found that is
patches it to make -buildmode=pie the default. I've tried to find why. I've
managed to find this thread
https://groups.google.com/forum/#!searchin/golang-nuts/pie|sort:date/golang-nuts/Jd9tlNc6jUE/Z9ldF6vPEAAJ
