[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Go & bundling
From: |
Ludovic Courtès |
Subject: |
Go & bundling |
Date: |
Tue, 26 Jul 2016 00:05:12 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
Leo Famulari <address@hidden> 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’.