Sun Aug 21 09:14:25 2016 UTC ()
New package, go-gls-4.2.0.
Every so often, a thread shows up on the golang-nuts asking for some form of
goroutine-local-storage, or some kind of goroutine id, or some kind of context.
There are a few valid use cases for goroutine-local-storage, one of the most
prominent being log line context. One poster was interested in being able to
log an HTTP request context id in every log line in the same goroutine as the
incoming HTTP request, without having to change every library and function call
he was interested in logging.
It is my duty to point you to https://blog.golang.org/context, which is how
Google solves all of the problems you'd perhaps consider using this package for
at scale.
(bsiegert)
diff -r1.2298 -r1.2299 pkgsrc/devel/Makefile
diff -r0 -r1.1 pkgsrc/devel/go-gls/DESCR
diff -r0 -r1.1 pkgsrc/devel/go-gls/Makefile
diff -r0 -r1.1 pkgsrc/devel/go-gls/PLIST
diff -r0 -r1.1 pkgsrc/devel/go-gls/buildlink3.mk
diff -r0 -r1.1 pkgsrc/devel/go-gls/distinfo
--- pkgsrc/devel/Makefile 2016/08/21 08:23:50 1.2298
+++ pkgsrc/devel/Makefile 2016/08/21 09:14:25 1.2299
| @@ -1,14 +1,14 @@ | | | @@ -1,14 +1,14 @@ |
1 | # $NetBSD: Makefile,v 1.2298 2016/08/21 08:23:50 taca Exp $ | | 1 | # $NetBSD: Makefile,v 1.2299 2016/08/21 09:14:25 bsiegert Exp $ |
2 | # | | 2 | # |
3 | | | 3 | |
4 | COMMENT= Development utilities | | 4 | COMMENT= Development utilities |
5 | | | 5 | |
6 | SUBDIR+= ETL | | 6 | SUBDIR+= ETL |
7 | SUBDIR+= ExmanIDE | | 7 | SUBDIR+= ExmanIDE |
8 | SUBDIR+= GConf | | 8 | SUBDIR+= GConf |
9 | SUBDIR+= GConf-ui | | 9 | SUBDIR+= GConf-ui |
10 | SUBDIR+= Gorm | | 10 | SUBDIR+= Gorm |
11 | SUBDIR+= MoarVM | | 11 | SUBDIR+= MoarVM |
12 | SUBDIR+= ObjectiveLib | | 12 | SUBDIR+= ObjectiveLib |
13 | SUBDIR+= ProjectCenter | | 13 | SUBDIR+= ProjectCenter |
14 | SUBDIR+= R-Rcpp | | 14 | SUBDIR+= R-Rcpp |
| @@ -285,26 +285,27 @@ SUBDIR+= global | | | @@ -285,26 +285,27 @@ SUBDIR+= global |
285 | SUBDIR+= gmake | | 285 | SUBDIR+= gmake |
286 | SUBDIR+= gmock | | 286 | SUBDIR+= gmock |
287 | SUBDIR+= gmp | | 287 | SUBDIR+= gmp |
288 | SUBDIR+= gmtk | | 288 | SUBDIR+= gmtk |
289 | SUBDIR+= gnatpython | | 289 | SUBDIR+= gnatpython |
290 | SUBDIR+= gnome-common | | 290 | SUBDIR+= gnome-common |
291 | SUBDIR+= gnustep-base | | 291 | SUBDIR+= gnustep-base |
292 | SUBDIR+= gnustep-examples | | 292 | SUBDIR+= gnustep-examples |
293 | SUBDIR+= gnustep-make | | 293 | SUBDIR+= gnustep-make |
294 | SUBDIR+= gnustep-objc | | 294 | SUBDIR+= gnustep-objc |
295 | SUBDIR+= gnustep-objc-lf2 | | 295 | SUBDIR+= gnustep-objc-lf2 |
296 | SUBDIR+= go-check | | 296 | SUBDIR+= go-check |
297 | SUBDIR+= go-flags-svent | | 297 | SUBDIR+= go-flags-svent |
| | | 298 | SUBDIR+= go-gls |
298 | SUBDIR+= go-ini | | 299 | SUBDIR+= go-ini |
299 | SUBDIR+= go-mow-cli | | 300 | SUBDIR+= go-mow-cli |
300 | SUBDIR+= go-nbreader | | 301 | SUBDIR+= go-nbreader |
301 | SUBDIR+= go-ratelimit | | 302 | SUBDIR+= go-ratelimit |
302 | SUBDIR+= go-review | | 303 | SUBDIR+= go-review |
303 | SUBDIR+= go-termbox | | 304 | SUBDIR+= go-termbox |
304 | SUBDIR+= go-testify | | 305 | SUBDIR+= go-testify |
305 | SUBDIR+= go-tools | | 306 | SUBDIR+= go-tools |
306 | SUBDIR+= gob2 | | 307 | SUBDIR+= gob2 |
307 | SUBDIR+= gobject-introspection | | 308 | SUBDIR+= gobject-introspection |
308 | SUBDIR+= golint | | 309 | SUBDIR+= golint |
309 | SUBDIR+= google-api-go-client | | 310 | SUBDIR+= google-api-go-client |
310 | SUBDIR+= google-glog | | 311 | SUBDIR+= google-glog |
Every so often, a thread shows up on the golang-nuts asking for some form of
goroutine-local-storage, or some kind of goroutine id, or some kind of context.
There are a few valid use cases for goroutine-local-storage, one of the most
prominent being log line context. One poster was interested in being able to
log an HTTP request context id in every log line in the same goroutine as the
incoming HTTP request, without having to change every library and function call
he was interested in logging.
It is my duty to point you to https://blog.golang.org/context, which is how
Google solves all of the problems you'd perhaps consider using this package for
at scale.
# $NetBSD: Makefile,v 1.1 2016/08/21 09:14:25 bsiegert Exp $
GITHUB_TAG= v4.2.0
DISTNAME= gls-${GITHUB_TAG:S/v//}
PKGNAME= go-${DISTNAME}
CATEGORIES= devel
MASTER_SITES= ${MASTER_SITE_GITHUB:=jtolds/}
MAINTAINER= pkgsrc-users@NetBSD.org
HOMEPAGE= https://github.com/jtolds/gls
COMMENT= Goroutine local storage
LICENSE= mit
WRKSRC= ${WRKDIR}
GO_DIST_BASE= ${DISTNAME}
GO_SRCPATH= github.com/jtolds/gls
.include "../../lang/go/go-package.mk"
.include "../../mk/bsd.pkg.mk"
@comment $NetBSD: PLIST,v 1.1 2016/08/21 09:14:25 bsiegert Exp $
gopkg/pkg/${GO_PLATFORM}/github.com/jtolds/gls.a
gopkg/src/github.com/jtolds/gls/LICENSE
gopkg/src/github.com/jtolds/gls/README.md
gopkg/src/github.com/jtolds/gls/context.go
gopkg/src/github.com/jtolds/gls/context_test.go
gopkg/src/github.com/jtolds/gls/gen_sym.go
gopkg/src/github.com/jtolds/gls/id_pool.go
gopkg/src/github.com/jtolds/gls/stack_tags.go
gopkg/src/github.com/jtolds/gls/stack_tags_js.go
gopkg/src/github.com/jtolds/gls/stack_tags_main.go
@pkgdir bin
# $NetBSD: buildlink3.mk,v 1.1 2016/08/21 09:14:25 bsiegert Exp $
BUILDLINK_TREE+= go-gls
.if !defined(GO_GLS_BUILDLINK3_MK)
GO_GLS_BUILDLINK3_MK:=
BUILDLINK_CONTENTS_FILTER.go-gls= ${EGREP} gopkg/
BUILDLINK_DEPMETHOD.go-gls?= build
BUILDLINK_API_DEPENDS.go-gls+= go-gls>=4.2.0
BUILDLINK_PKGSRCDIR.go-gls?= ../../devel/go-gls
.endif # GO_GLS_BUILDLINK3_MK
BUILDLINK_TREE+= -go-gls
$NetBSD: distinfo,v 1.1 2016/08/21 09:14:25 bsiegert Exp $
SHA1 (gls-4.2.0.tar.gz) = 6fa513402b6571eaa564cee4f27b5261de49cae1
RMD160 (gls-4.2.0.tar.gz) = 5079484ad141a888941ab1648d772f8b94302cd5
SHA512 (gls-4.2.0.tar.gz) = 1bf9e8c7ab69c8754173129f16b1ac81e2635c75cbdfd9be34ca019b47a64ce489f29bdef3c35c2ef2e9ea60ba441b6b5f1417eec393733bc6dc62f9e017adc3
Size (gls-4.2.0.tar.gz) = 6464 bytes