all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Sharlatan Hellseher <sharlatanus@gmail.com>
To: Ekaitz Zarraga <ekaitz@elenq.tech>
Cc: 68423@debbugs.gnu.org, Picnoir <picnoir@alternativebit.fr>,
	Katherine Cox-Buday <cox.katherine.e+guix@gmail.com>
Subject: [bug#68423] [PATCH] guix: go-build-system: use trimpath go flag
Date: Tue, 23 Jan 2024 20:34:50 +0000	[thread overview]
Message-ID: <CAO+9K5roW33yFyxbHn6qYigNmzHbTeXrtwWzT4P0VBn9BVb8Mg@mail.gmail.com> (raw)
In-Reply-To: <5171475c-288e-24c2-a91c-94ee9b7627af@elenq.tech>

[-- Attachment #1: Type: text/plain, Size: 647 bytes --]

Hi Ekaitz,

> With the previous alternative the packager would just remove
> the phase, but hardcoding the option as we did doesn't provide
> any way to do that...  Some kind of flag should be enough.

It would be great to have more control over golang build envars
and build flags, like it happen in gnu-build-system or cmake-build-system
via #:make-flags and #:configure-flags.

Having some common defaults hardcoded and kind of #:build-flags as a way to
path anything else to compiler.

There is a similar thread referring go test flags, I've listed all in here:
https://mail.gnu.org/archive/html/guix-devel/2024-01/msg00235.html

Thanks,
Oleg

[-- Attachment #2: Type: text/html, Size: 1128 bytes --]

  reply	other threads:[~2024-01-23 20:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-13 11:46 [bug#68423] [PATCH] guix: go-build-system: use trimpath go flag Ekaitz Zarraga
2024-01-13 12:58 ` Sharlatan Hellseher
2024-01-13 13:31   ` Ekaitz Zarraga
2024-01-23 20:34     ` Sharlatan Hellseher [this message]
2024-03-07 12:21 ` bug#68423: " Sharlatan Hellseher

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=CAO+9K5roW33yFyxbHn6qYigNmzHbTeXrtwWzT4P0VBn9BVb8Mg@mail.gmail.com \
    --to=sharlatanus@gmail.com \
    --cc=68423@debbugs.gnu.org \
    --cc=cox.katherine.e+guix@gmail.com \
    --cc=ekaitz@elenq.tech \
    --cc=picnoir@alternativebit.fr \
    /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.