unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Peter Polidoro <peter@polidoro.io>
To: help-guix@gnu.org
Subject: Finding Dependencies at Run Time
Date: Wed, 13 Jul 2022 10:56:27 -0400	[thread overview]
Message-ID: <8EA69D34-498D-4172-B0E4-C90E59009F68@polidoro.io> (raw)

I apologize for a very basic question, but I could not find where this is documented. If a paper or manual page describes this I would be happy to read it.

How, in general, does code in a Guix package find its dependency packages at run time?

Does it potentially work differently for each build system or is the same approach used for all packages?

Are absolute store paths of the dependencies saved at build time in environment variables or symbolic links or something that are accessible to the run time code?

If code in a package looks for dependencies using relative paths, are copies or links to the dependencies saved within the package? Or is that sort of duplication always avoided? Are relative paths converted to absolute store paths somehow?

Is the Guix daemon needed at run time to help packages find each other or is the information needed to resolve all of the dependencies saved into the package at build time?

Thanks!

             reply	other threads:[~2022-07-13 14:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13 14:56 Peter Polidoro [this message]
2022-07-13 16:03 ` Finding Dependencies at Run Time Julien Lepiller
2022-07-13 17:47   ` Peter Polidoro
2022-07-13 18:39     ` Julien Lepiller
2022-07-13 18:51       ` Peter Polidoro
2022-07-13 21:02         ` Julien Lepiller
2022-07-14 17:47           ` Peter Polidoro
2022-07-16 21:53             ` Thiago Jung Bauermann
2022-07-14  8:25         ` Ricardo Wurmus
2022-07-14  8:48           ` Philip McGrath
2022-07-14 11:28             ` Ricardo Wurmus
2022-07-14 13:27               ` 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

  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=8EA69D34-498D-4172-B0E4-C90E59009F68@polidoro.io \
    --to=peter@polidoro.io \
    --cc=help-guix@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. 
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).