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

Hi,

zimoun <zimon.toutoune@gmail.com> skribis:

> 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?

‘guix pull’ builds Guix using the method implemented in (guix self).
The entry point there is ‘compiled-guix’, which returns a compiled Guix.

It’s not a package so the package API doesn’t apply.

HTH,
Ludo’.




  reply	other threads:[~2021-02-24 11:14 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
2021-02-24 11:11     ` Ludovic Courtès [this message]
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=87sg5l3ekn.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=46650@debbugs.gnu.org \
    --cc=contact@carldong.me \
    --cc=zimon.toutoune@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.
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.