FreeBSD ports you maintain which are out of date

Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you

Re: How to handle go dependencies

Am 22.06.2019 um 22:52 schrieb Dmitri Goutnik: > Can be further simplified by using USES=go:modules. This will remove the need > to modify MAKE_ENV as go.mk will then add -mod=vendor flag automagically. very interesting. I also found a nice mechanism in devel/bingo. It has a very nice awk script

Re: How to handle go dependencies

On Sun, Jun 23, 2019 at 11:47:41AM +0200, Matthias Fechner wrote: > Am 22.06.2019 um 22:52 schrieb Dmitri Goutnik: > > Can be further simplified by using USES=go:modules. This will remove the > > need > > to modify MAKE_ENV as go.mk will then add -mod=vendor flag automagically. > > very interest

Re: How to handle go dependencies

Hi! > Please do not use it. It is broken in many ways. Use Dimtri's > devel/modules2tuple instead. Change to WRKSRC of your port and run > `go mod vendor` then `modules2tuple vendor/modules.txt` and it will > spit out an appropriate GH_TUPLE etc. Thanks, I tested that approach with an updated

Re: How to handle go dependencies

On Sun, Jun 23, 2019 at 12:30:00PM +0200, Kurt Jaeger wrote: > Hi! > > > Please do not use it. It is broken in many ways. Use Dimtri's > > devel/modules2tuple instead. Change to WRKSRC of your port and run > > `go mod vendor` then `modules2tuple vendor/modules.txt` and it will > > spit out an a

Re: How to handle go dependencies

Hi! [...] > > can't load package: package github.com/osrg/gobgp/gobgpd: cannot find > > package "github.com/osrg/gobgp/gobgpd" in any of: > > /usr/local/go/src/github.com/osrg/gobgp/gobgpd (from $GOROOT) > > /home/pi/m/net/gobgp/work/src/github.com/osrg/gobgp/gobgpd (from > > $GOPATH) >

Re: How to handle go dependencies

On 19-06-23 12:47:22, Kurt Jaeger wrote: > Hi! > > [...] > > > can't load package: package github.com/osrg/gobgp/gobgpd: cannot find > > > package "github.com/osrg/gobgp/gobgpd" in any of: > > > /usr/local/go/src/github.com/osrg/gobgp/gobgpd (from $GOROOT) > > > /home/pi/m/net/gobgp/work/src/

Re: How to handle go dependencies

Hi! Dimitri wrote: > It appears that upstream moved gobgp and gobgpd packages to ./cmd, so > GO_TARGET needs to be updated: > > -GO_TARGET= ${GO_PKGNAME}/gobgp \ > - ${GO_PKGNAME}/gobgpd > +GO_TARGET= ./cmd/gobgp \ > + ./cmd/gobgpd Thanks, it seems to build.

Switching to openssl111

FreeBSD 12.0-RELEASE-p6 GENERIC amd64 openssl version: OpenSSL 1.0.2s 28 May 2019 I want to use openssl111 so I can take advantage of 'tls 1.3' with postfix and apache24. I am trying to determine the correct procedure to use. I am using poudriere to build my packages and then install them. 1) M

Re: How to handle go dependencies

Am 23.06.2019 um 11:57 schrieb Tobias Kortkamp: > Please do not use it. It is broken in many ways. Use Dimtri's > devel/modules2tuple instead. Change to WRKSRC of your port and run > `go mod vendor` then `modules2tuple vendor/modules.txt` and it will > spit out an appropriate GH_TUPLE etc. than

Re: Switching to openssl111

On 2019-06-23 7:22, Carmel NY wrote: FreeBSD 12.0-RELEASE-p6 GENERIC amd64 openssl version: OpenSSL 1.0.2s 28 May 2019 I want to use openssl111 so I can take advantage of 'tls 1.3' with postfix and apache24. I am trying to determine the correct procedure to use. I am using poudriere to build m

Re: How to handle go dependencies

On 19-06-23 22:21:44, Matthias Fechner wrote: > Am 23.06.2019 um 11:57 schrieb Tobias Kortkamp: > > Please do not use it. It is broken in many ways. Use Dimtri's > > devel/modules2tuple instead. Change to WRKSRC of your port and run > > `go mod vendor` then `modules2tuple vendor/modules.txt` and

libuv

Is it just me or. # cd /usr/ports/devel/libuv/ ; make all ===> libuv-1.29.1 depends on package: autoconf>=2.69 - found ===> libuv-1.29.1 depends on package: automake>=1.16.1 - found ===> libuv-1.29.1 depends on executable: libtoolize - found ===> libuv-1.29.1 depends on package: pkg

Re: libuv

On Mon, 24 Jun 2019 at 10:27, Andy Farkas wrote: > > > Is it just me or. > > # cd /usr/ports/devel/libuv/ ; make all > ===> libuv-1.29.1 depends on package: autoconf>=2.69 - found > ===> libuv-1.29.1 depends on package: automake>=1.16.1 - found > ===> libuv-1.29.1 depends on executable:

Re: libuv

> On Jun 24, 2019, at 7:45, Jonathan Chen wrote: > >> On Mon, 24 Jun 2019 at 10:27, Andy Farkas wrote: >> >> >> Is it just me or. >> >> # cd /usr/ports/devel/libuv/ ; make all >> ===> libuv-1.29.1 depends on package: autoconf>=2.69 - found >> ===> libuv-1.29.1 depends on package: a

Re: libuv

On Mon, 24 Jun 2019 at 11:20, wrote: > > > On Jun 24, 2019, at 7:45, Jonathan Chen wrote: > > > >> On Mon, 24 Jun 2019 at 10:27, Andy Farkas wrote: > >> > >> > >> Is it just me or. > >> > >> # cd /usr/ports/devel/libuv/ ; make all > >> ===> libuv-1.29.1 depends on package: autoconf>=2.69 -

Re: libuv

On 24/06/2019 08:45, Jonathan Chen wrote: On Mon, 24 Jun 2019 at 10:27, Andy Farkas wrote: Is it just me or. # cd /usr/ports/devel/libuv/ ; make all ===> libuv-1.29.1 depends on package: autoconf>=2.69 - found ===> libuv-1.29.1 depends on package: automake>=1.16.1 - found ===> libuv