unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Stephen Scheck <singularsyntax@gmail.com>
To: Christopher Baines <mail@cbaines.net>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Name resolution failures during build
Date: Fri, 20 Nov 2020 17:55:50 -0500	[thread overview]
Message-ID: <CAKjnHz2vthUK6OKK0BZOT9uB4Ee2KZa8rAU2nJPq9+rvV4yxFA@mail.gmail.com> (raw)
In-Reply-To: <87a6vbk90r.fsf@cbaines.net>

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?

On Fri, Nov 20, 2020 at 4:34 PM Christopher Baines <mail@cbaines.net> wrote:

>
> Stephen Scheck <singularsyntax@gmail.com> writes:
>
> > Sure - I understand the reasoning - but this is an open-source project
> with
> > its own build system that I'm trying to package, and I believe its build
> > system depends on network access (it's Go-based, and my understanding is
> > that the Go dependency model relies on access to numerous external Git
> > repos). Is such a project unsupportable by Guix?
>
> Not at all, there's a number of examples of software written in Go
> packaged for Guix, it's just that you need to build it in a way that
> doesn't depend on network access.
>
> Keeping this as a hard requirement is one of the reasons why having Guix
> packages is beneficial. If some packages used the network during builds,
> you'd end up in the bad situation where packages would be far more
> likely to fail to build, now or in the future, and it would be harder to
> reason about build reproducibility (due to the interaction with the
> network).
> Message-ID: <87blfrk912.fsf@cbaines.net>
>

  reply	other threads:[~2020-11-20 22:56 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 [this message]
2020-11-21 19:22   ` Efraim Flashner
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=CAKjnHz2vthUK6OKK0BZOT9uB4Ee2KZa8rAU2nJPq9+rvV4yxFA@mail.gmail.com \
    --to=singularsyntax@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=mail@cbaines.net \
    /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).