From: Efraim Flashner <efraim@flashner.co.il>
To: Stephen Scheck <singularsyntax@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Name resolution failures during build
Date: Sat, 21 Nov 2020 21:22:09 +0200 [thread overview]
Message-ID: <20201121192209.GC1088@E5400> (raw)
In-Reply-To: <CAKjnHz2vthUK6OKK0BZOT9uB4Ee2KZa8rAU2nJPq9+rvV4yxFA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
On Fri, Nov 20, 2020 at 05:55:50PM -0500, Stephen Scheck wrote:
> The project I'm attempting to package is a standalone application, with a
> Makefile build system entrypoint - it is not a library, so I don't think
> `go-build-system` is of any help here (though presumably the Makefile uses
> golang build machinery under the covers).
>
> Do any examples of standalone applications written in Go that are already
> packaged for Guix jump to mind?
>
Don't look at syncthing, it needs a bunch of hand holding to compile
correctly.
containerd and docker-cli in gnu/packages/docker.scm are two examples of
packages with binaries as outputs. I have a WIP package for keybase but
there's a large number of unpackaged dependencies so I've only gotten
some of them patched out.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-11-21 19:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 21:34 Name resolution failures during build Christopher Baines
2020-11-20 22:55 ` Stephen Scheck
2020-11-21 19:22 ` Efraim Flashner [this message]
2020-11-21 20:38 ` raingloom
-- strict thread matches above, loose matches on Subject: below --
2020-11-20 20:09 Stephen Scheck
2020-11-20 20:47 ` Christopher Baines
2020-11-20 21:15 ` Stephen Scheck
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201121192209.GC1088@E5400 \
--to=efraim@flashner.co.il \
--cc=help-guix@gnu.org \
--cc=singularsyntax@gmail.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).