> I can also generate a very large set of ports with it!
If you're interested in examples of things that don't work with this,
here are a couple I ran into.
github.com/tomnomnom/gron
github.com/gcla/termshark/v2
On Sat, 18 Apr 2020 at 11:26:34 +0100, Stuart Henderson wrote:
> On 2020/04/18 10:00, Landry Breuil wrote:
> > can be polished in-tree if needed, as long as all existing go ports
>
> > still build fine with the go.port.mk changes
On Sat, Apr 18, 2020 at 10:00:45AM +0200, Landry Breuil wrote:
> On Fri, Apr 17, 2020 at 05:26:58PM -0600, Aaron Bieber wrote:
> > Round... 10?
> Cant comment on the portgen perl bits (afresh1@ did :), but unless
> someone has an opposition against it, i think it's a nice addition that
> can be p
On 2020/04/18 10:00, Landry Breuil wrote:
> can be polished in-tree if needed, as long as all existing go ports
> still build fine with the go.port.mk changes i dont see harm in
> co
On Fri, Apr 17, 2020 at 05:26:58PM -0600, Aaron Bieber wrote:
> On Wed, 15 Apr 2020 at 18:56:09 -0600, Aaron Bieber wrote:
> > On Mon, 06 Apr 2020 at 17:15:17 -0600, Aaron Bieber wrote:
> > > Round two! This time with espie@'s bsd.port.mk fix:
> > > https://marc.info/?l=openbsd-ports-cvs&m=15861835
On Fri, Apr 17, 2020 at 05:26:58PM -0600, Aaron Bieber wrote:
> On Wed, 15 Apr 2020 at 18:56:09 -0600, Aaron Bieber wrote:
> > On Mon, 06 Apr 2020 at 17:15:17 -0600, Aaron Bieber wrote:
> > > Round two! This time with espie@'s bsd.port.mk fix:
> > > https://marc.info/?l=openbsd-ports-cvs&m=15861835
On Wed, 15 Apr 2020 at 18:56:09 -0600, Aaron Bieber wrote:
> On Mon, 06 Apr 2020 at 17:15:17 -0600, Aaron Bieber wrote:
> > Round two! This time with espie@'s bsd.port.mk fix:
> > https://marc.info/?l=openbsd-ports-cvs&m=158618354824687&w=2
> >
> > This resolves the issue with the conversion of [A
On Mon, 06 Apr 2020 at 17:15:17 -0600, Aaron Bieber wrote:
> Round two! This time with espie@'s bsd.port.mk fix:
> https://marc.info/?l=openbsd-ports-cvs&m=158618354824687&w=2
>
> This resolves the issue with the conversion of [A-Z] letters to ![a-z] in the
> package path.
>
> With this diff I ca
On Mon, Apr 13, 2020 at 08:44:47AM +0200, Landry Breuil wrote:
> On Mon, Apr 06, 2020 at 05:15:17PM -0600, Aaron Bieber wrote:
> > Round two! This time with espie@'s bsd.port.mk fix:
> > https://marc.info/?l=openbsd-ports-cvs&m=158618354824687&w=2
> >
> > This resolves the issue with the conversio
On Mon, Apr 06, 2020 at 05:15:17PM -0600, Aaron Bieber wrote:
> Round two! This time with espie@'s bsd.port.mk fix:
> https://marc.info/?l=openbsd-ports-cvs&m=158618354824687&w=2
>
> This resolves the issue with the conversion of [A-Z] letters to ![a-z] in the
> package path.
>
> With this diff I
Round two! This time with espie@'s bsd.port.mk fix:
https://marc.info/?l=openbsd-ports-cvs&m=158618354824687&w=2
This resolves the issue with the conversion of [A-Z] letters to ![a-z] in the
package path.
With this diff I can generate ports for the following without issue:
github.com/jrick/do
On Wed, 11 Dec 2019 at 15:30:43 +, Stuart Henderson wrote:
> The go.port.mk part of this breaks some existing ports e.g. net/dnscontrol,
> net/wireguard-go.
>
Here is a diff against the current ports tree - wireguard-go and dnscontrol
build fine.
I also tested other "MODGO_TYPE={bin,lib}" p
On Wed, 11 Dec 2019 at 15:30:43 +, Stuart Henderson wrote:
> The go.port.mk part of this breaks some existing ports e.g. net/dnscontrol,
> net/wireguard-go.
>
Here is a version of go.port.mk that fixes the GH_* ALL_TARGET stuff.
# $OpenBSD: go.port.mk,v 1.27 2019/11/19 09:17:06 sthen Exp $
The go.port.mk part of this breaks some existing ports e.g. net/dnscontrol,
net/wireguard-go.
On Sun, 08 Dec 2019 at 13:53:40 -0800, Andrew Hewus Fresh wrote:
> On Sun, Dec 08, 2019 at 11:42:50AM -0700, Aaron Bieber wrote:
> > Here is a diff that adds go support in portgen(1). It's a combination
> > of diffs from my self and afresh1@. There are a few issues, but on the
> > whole this is the
On Sun, Dec 08, 2019 at 11:42:50AM -0700, Aaron Bieber wrote:
> Here is a diff that adds go support in portgen(1). It's a combination
> of diffs from my self and afresh1@. There are a few issues, but on the
> whole this is the direction I think we should take with regard to
> porting Go application
Hi,
Here is a diff that adds go support in portgen(1). It's a combination
of diffs from my self and afresh1@. There are a few issues, but on the
whole this is the direction I think we should take with regard to
porting Go application.
The biggest issue with the diff is it's inability to cope with
17 matches
Mail list logo
