From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Go & bundling
Date: Tue, 26 Jul 2016 00:05:12 +0200 [thread overview]
Message-ID: <87k2g9cr1j.fsf_-_@gnu.org> (raw)
In-Reply-To: <20160725195006.GA532@jasmine> (Leo Famulari's message of "Mon, 25 Jul 2016 15:50:06 -0400")
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.
> I don't fully understand Debian's packaging, but it seems that they only
> use external packages to provide 2 of 39 dependencies, bootstrap and
> font-awesome:
> https://anonscm.debian.org/git/pkg-go/packages/syncthing.git/tree/debian/rules#n42
It might be that even the bravest have given up. ;-)
Ludo’.
next prev parent reply other threads:[~2016-07-25 22:05 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 ` Ludovic Courtès [this message]
2016-07-26 1:56 ` Go & bundling Catonano
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=87k2g9cr1j.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.