From: Catonano <catonano@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Go & bundling
Date: Tue, 26 Jul 2016 03:56:02 +0200 [thread overview]
Message-ID: <CAJ98PDwWTWOKNL+dG9456UEVJZ4+nxTVTxyPj51vZ+LyDUC8XQ@mail.gmail.com> (raw)
In-Reply-To: <87k2g9cr1j.fsf_-_@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]
2016-07-26 0:05 GMT+02:00 Ludovic Courtès <ludo@gnu.org>:
> 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 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 “unbundle” if they want to. Much more transparent 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 ?
[-- Attachment #2: Type: text/html, Size: 1881 bytes --]
next prev parent reply other threads:[~2016-07-26 1:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 21:36 Go build system Leo Famulari
2016-07-24 22:25 ` Ludovic Courtès
2016-07-25 8:47 ` Andy Wingo
2016-07-25 19:50 ` Leo Famulari
2016-07-25 22:05 ` Go & bundling Ludovic Courtès
2016-07-26 1:56 ` Catonano [this message]
2016-07-26 4:06 ` Alex Griffin
2016-07-26 12:07 ` Alex Griffin
2016-08-02 20:50 ` Leo Famulari
2016-07-26 6:33 ` Go build system Christopher Baines
2016-08-02 20:42 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ98PDwWTWOKNL+dG9456UEVJZ4+nxTVTxyPj51vZ+LyDUC8XQ@mail.gmail.com \
--to=catonano@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.