unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Packaging gx (for IPFS): Need to update default Go to 1.11?
Date: Tue, 6 Nov 2018 12:31:16 -0500	[thread overview]
Message-ID: <20181106173116.GA3232@jasmine.lan> (raw)
In-Reply-To: <878t26b0i1.fsf@ambrevar.xyz>

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

On Tue, Nov 06, 2018 at 06:04:54PM +0100, Pierre Neidhardt wrote:
> Actually bug 32919 matters, it breaks Demlo and all packages that depend on
> packages that need special compilation flags (e.g. -tags "xyz").
> 
> Concretely, say A depends on B and B must be built with "-tags xyz".
> When packaging B, we produce a pkg.
> If we try to package A _without the tags flag_, since B is not re-used, Go will
> rebuild B without the flag which will not produce the desired result.
> 
> The most obvious workaround is to pass the right flags to A.  But if A needs
> different flags, then we are stuck.
> 
> Conclusion: we need to update the build system! :D

Hm, quel dommage!

If most of the Go packages are ready for Go 1.11, we could make it the
dfeault and then use Go 1.9 for the packages that are lagging behind. Or
vice versa.

In general, we should try to move to 1.11 since 1.9 is no longer
supported upstream.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-11-06 17:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-24 11:40 Packaging gx (for IPFS): Need to update default Go to 1.11? Pierre Neidhardt
2018-10-24 11:42 ` Pierre Neidhardt
2018-10-24 13:55 ` Leo Famulari
2018-10-24 14:02   ` Pierre Neidhardt
2018-10-24 14:14     ` Leo Famulari
2018-11-06 11:56       ` Pierre Neidhardt
2018-11-06 12:03         ` Pierre Neidhardt
2018-11-06 17:04           ` Pierre Neidhardt
2018-11-06 17:31             ` Leo Famulari [this message]
2018-11-06 17:33               ` Pierre Neidhardt
2018-11-06 19:57                 ` Leo Famulari
2018-11-07  7:33                   ` Pierre Neidhardt
2018-11-07 16:22                     ` Pierre Neidhardt
2018-11-07 18:26                       ` Leo Famulari
2018-11-07 20:09                         ` Pierre Neidhardt
2018-11-07 20:40                           ` Leo Famulari
2018-11-07 20:48                             ` Pierre Neidhardt
2018-11-07 21:03                               ` Leo Famulari
2018-11-11 16:43                                 ` Pierre Neidhardt
2018-11-11 20:52                                   ` Pierre Neidhardt
2018-11-11 21:33                                     ` Pierre Neidhardt
2018-11-12  9:45                                       ` Pierre Neidhardt
2018-11-12 17:33                                         ` Leo Famulari

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=20181106173116.GA3232@jasmine.lan \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).