From mboxrd@z Thu Jan 1 00:00:00 1970 From: Catonano Subject: Re: Go & bundling Date: Tue, 26 Jul 2016 03:56:02 +0200 Message-ID: References: <20160711213621.GA22573@jasmine> <87mvl68yhn.fsf@gnu.org> <20160725195006.GA532@jasmine> <87k2g9cr1j.fsf_-_@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a113fb6b006499b0538803497 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54706) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bRrbM-00082a-IB for guix-devel@gnu.org; Mon, 25 Jul 2016 21:56:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bRrbL-00010r-BT for guix-devel@gnu.org; Mon, 25 Jul 2016 21:56:08 -0400 In-Reply-To: <87k2g9cr1j.fsf_-_@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: =?UTF-8?Q?Ludovic_Court=C3=A8s?= Cc: guix-devel@gnu.org --001a113fb6b006499b0538803497 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 2016-07-26 0:05 GMT+02:00 Ludovic Court=C3=A8s : > Leo Famulari skribis: > > > We will have to decide what to do about bundled dependencies. Bundling > > the source code of dependencies appears to be standard practice in the > > world of Go. > > Bundling appears to be standard practice in the world. > :-) > > > The compiler began supporting this directly in the 1.5 series: > > > https://github.com/golang/go/wiki/PackageManagementTools#go15vendorexperi= ment > > > > This is the manifest of Syncthing's dependencies, which are bundled in > > the same directory: > > https://github.com/syncthing/syncthing/blob/master/vendor/manifest > > > > If that manifest is a standard thing, we could make a go-importer that > > used it to create new packages. > > Indeed, that would be pretty cool as it effectively provides an easy way > for users to =E2=80=9Cunbundle=E2=80=9D if they want to. Much more trans= parent that > what is often practiced. > The "new packages" indicated in the manifest could, in turn, have bundled dependencies. So the importer should be a recursive one. Like the one that Jelle is using for npm. Right ? --001a113fb6b006499b0538803497 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
2016-07-26 0:05 GMT+02:00 Ludovic Court=C3=A8s <ludo@gnu.org= >:
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">Leo Famulari <leo@famulari.name> skribis:

> We will have to decide what to do about bundled dependencies. Bundling=
> the source code of dependencies appears to be standard practice in the=
> world of Go.

Bundling appears to be standard practice in the world.
:-)

> The compiler began supporting this directly in the 1.5 series:
> https://github.com= /golang/go/wiki/PackageManagementTools#go15vendorexperiment
>
> This is the manifest of Syncthing's dependencies, which are bundle= d in
> the same directory:
> https://github.com/syncthing/= syncthing/blob/master/vendor/manifest
>
> If that manifest is a standard thing, we could make a go-importer that=
> used it to create new packages.

Indeed, that would be pretty cool as it effectively provides an easy way for users to =E2=80=9Cunbundle=E2=80=9D if they want to.=C2=A0 Much more tr= ansparent that
what is often practiced.

The "new = packages" indicated in the manifest could, in turn, have bundled depen= dencies. So the importer should be a recursive one.

Like = the one that Jelle is using for npm.

Right ?

--001a113fb6b006499b0538803497--