all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>, "Carl Dong" <contact@carldong.me>
Cc: 46650@debbugs.gnu.org
Subject: bug#46650: Extending package transformation options
Date: Tue, 23 Feb 2021 23:22:11 +0100	[thread overview]
Message-ID: <86pn0qtofg.fsf@gmail.com> (raw)
In-Reply-To: <87h7m6j0yi.fsf@gnu.org>

Hi,

On Sat, 20 Feb 2021 at 14:57, Ludovic Courtès <ludo@gnu.org> wrote:

> Guix as returned by ‘guix pull’ and ‘guix time-machine’ depends on
> GnuTLS.  So here, we have a special case: to build Guix itself, you need
> to build GnuTLS first, and there’s no way to pass ‘--without-tests’ at
> that level.
>
> I’m not sure how to change that because unfortunately, ‘guix pull’ and
> ‘time-machine’ don’t even know that Guix depends on GnuTLS; only the
> target Guix knows about this.  :-/

If  «“guix pull” and ’time-machine’ don’t even know that Guix depends on
GnuTLS» and «to build Guix itself, you need to build GnuTLS first», how
does it work?  How does «you» know that they needs to build GnuTLS
first?

Well, I do not know if it is viable, one hack should to use the package
Guix to collect this missing knowledge.  Why is it not possible to build
all the package dependencies of Guix with the option --without-tests?


Cheers,
simon




  reply	other threads:[~2021-02-23 22:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 23:24 bug#46650: Extending package transformation options Carl Dong
2021-02-20  0:17 ` Leo Famulari
2021-02-20 14:00   ` Ludovic Courtès
2021-02-20 13:57 ` Ludovic Courtès
2021-02-23 22:22   ` zimoun [this message]
2021-02-24 11:11     ` Ludovic Courtès
2021-02-24 13:43       ` zimoun
2021-02-24 17:21         ` Ludovic Courtès
2021-02-26 21:44           ` zimoun

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=86pn0qtofg.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=46650@debbugs.gnu.org \
    --cc=contact@carldong.me \
    --cc=ludo@gnu.org \
    /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.