all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: "(" <paren@disroot.org>
Cc: 64090@debbugs.gnu.org, Robby Zambito <contact@robbyzambito.me>
Subject: bug#64090: Cannot compute a file with a G-exp
Date: Tue, 10 Sep 2024 17:01:47 +0200	[thread overview]
Message-ID: <87r09rd02s.fsf@gmail.com> (raw)
In-Reply-To: <87edmadp72.fsf@disroot.org> (paren@disroot.org's message of "Sat, 17 Jun 2023 17:27:46 +0100")

Hi,

On Sat, 17 Jun 2023 at 17:27, "(" <paren@disroot.org> wrote:
> Robby Zambito <contact@robbyzambito.me> writes:
>> Strangely with-extensions doesn't seem to be including the whole
>> dependency tree for me. Should it?
>
> No, I don't think it should. It *would* be possible to traverse the
> package inputs and add all the GUILE-BUILD-SYSTEM-using packages, but
> then you get the problem that not all Guile packages have their
> dependencies specified in the INPUTS list (for some reason, IIRC, you
> need the Guile dependencies to be in both INPUTS *and* NATIVE-INPUTS,
> but some have them only in NATIVE-INPUTS).
>
> The problem there is that if you have a dependency that's only in
> NATIVE-INPUTS, it's difficult to tell if it's actually used by the
> application or by, say, a build script.

Reading the thread and from my understanding, there is no bug.  Closing?

Else, could you provide more information about the bug?

Cheers,
simon




      reply	other threads:[~2024-09-10 16:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16  1:17 bug#64090: Cannot compute a file with a G-exp Robby Zambito
2023-06-17  7:51 ` paren--- via Bug reports for GNU Guix
2023-06-17 14:05   ` Robby Zambito
2023-06-17 16:27     ` paren--- via Bug reports for GNU Guix
2024-09-10 15:01       ` Simon Tournier [this message]

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=87r09rd02s.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=64090@debbugs.gnu.org \
    --cc=contact@robbyzambito.me \
    --cc=paren@disroot.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.