Re: pkg/52747: new package submission for influxdb 1.4.2

["H. William Welliver III" <william%welliver.org@localhost>]

The following reply was made to PR pkg/52747; it has been noted by GNATS.

From: "H. William Welliver III" <william%welliver.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: pkg/52747: new package submission for influxdb 1.4.2
Date: Sat, 6 Jan 2018 13:55:53 -0500

 Hi,
 
 Thanks for the feedback. The restriction on fetching outside of the =
 fetch action makes complete sense.  I=E2=80=99m not opposed to creating =
 a package for the gdm dependency manager=E2=80=A6 it seems reasonable to =
 make the tool available as a package.=20
 
 However, after doing more research, I think that go software building =
 seems determined to operate in opposition to that concept: influxdb, for =
 example, has 20 or more dependencies, some of which are only available =
 as git checkouts (which is what the gdm tool is being used to fetch and =
 manage). Since each of those dependencies are based on a particular =
 commit id, I=E2=80=99m not sure that it would be feasible to create =
 packages for each dependency.=20
 
 Would an acceptable alternative be to create a distribution file that =
 contained the particular go files required by a particular version of =
 influxdb and make that available on, say, GitHub? That way, a canonical =
 set of source would be available for download by pkgsrc and the build =
 could proceed without any additional network access?=