From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: How to package go-sqlite3, go-fuse, and finally TMSU? Date: Fri, 21 Jul 2017 13:55:29 -0400 Message-ID: <20170721175529.GA8855@jasmine.lan> References: <878tk8kz1o.fsf@gmail.com> <20170721144531.agpeoavy6tevpqbw@abyayala> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="envbJBWh7q8WU6mo" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59633) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dYc9I-0007mA-Qi for guix-devel@gnu.org; Fri, 21 Jul 2017 13:55:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dYc9F-0001v6-Oi for guix-devel@gnu.org; Fri, 21 Jul 2017 13:55:36 -0400 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:56159) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dYc9F-0001ue-DG for guix-devel@gnu.org; Fri, 21 Jul 2017 13:55:33 -0400 Content-Disposition: inline In-Reply-To: <20170721144531.agpeoavy6tevpqbw@abyayala> 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: Mekeor Melire , guix-devel@gnu.org --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 21, 2017 at 02:45:31PM +0000, ng0 wrote: > Mekeor Melire transcribed 0.8K bytes: > > But how to package go-libraries for Guix? We don't have a > > go-build-system. On usual distributions, you install these libraries > > either with `go get github.com/mattn/go-sqlite3` or `go install > > github.com/mattn/go-sqlite3`. In fact, Nix just downloads those two > > libraries to the same directory as TMSU: >=20 > I don't see any replies to this, so: > I think the current state of the go-build-system is that someone > (Pjotr?) started working on it but it needs someone with more experience > in Go to get this finished. It was Petter that shared a prototype go-build-system. Recently I read it carefully and have a good idea of how to proceed. I plan to finish it eventually but I'm happy to share what I learned with anyone else who is interested in doing the work. > There is 'syncthing' which someone has packaged, maybe you could look at > it and apply something similar. That package is here: https://github.com/lfam/pkgs/blob/master/leo/packages/syncthing.scm It shows a bit about how Go software expects to be built, but not the whole story. It uses the bundled dependencies, so it doesn't illustrate how the dependencies need to be laid out in a filesystem union relative to the Syncthing source code. --envbJBWh7q8WU6mo Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAllyQBEACgkQJkb6MLrK fwgSpw/8CchdF8d1Kj+yObPzRhX2oOjewygTYzPMH8SP/ixdkh1s6p0dvuU8IE5/ FY7P1hcOZxjpcOm2rAdFZGL39lOptKbNAT/nNpXTl0Y5oeToAuaGr4aX6TFUoTwi 4qOpdhaBRo/IgH1UetCzzkmqO67UbwbEhbqj8QtYFCd2h4whirHxLWYlwM/pUy9t prXK8ID+Z5xMyxGSalHg9gvbflDGczqlrQjz9YM7kDHp4X5Bwj3IlG1VwbLPGxBT IelMsADgs1d/+67vIsp+h9d9/R32CGghFae2UigCHo0I7c2o/PvRZehXeUn+NOIz w8Yeg0vqWCs4KnnQ4z5o7iHyxKmkvGec/D2pSnxyvTAPX8VieVFJtxat/49FVwrs gGpmFweq1QNp/IqkkWcuLjqJ5vN3tS+1v72iGlVwGnhQ+qcfxQRJBKdk0FM3l+y4 mvz5AVm6yj5Xtj6r2rN9EgZGMaBzWJ5PzCTGznAa3iZxuCj+EsRCnrob2ZauflOY GNVKTUdLfFr5xTNrb62VEKxQci5FLC1hxtPXnG1VfFq5DWtSf1eDzPCchBMyqgY7 1XoPnl8XY2ysOVRVJvzbuTnQoocj6nGUk2MyAfin/Sb4p+8qVDF5tsr3f5GUWsdX F6NFyuWABcJwbNmxZFI0dTMMH8ZI9iXOPX5KN42SjV4LiUYeVy4= =vr2x -----END PGP SIGNATURE----- --envbJBWh7q8WU6mo--