From: Suhail Singh <suhailsingh247@gmail.com>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: Suhail Singh <suhailsingh247@gmail.com>,
Guix-devel mailing list <guix-devel@gnu.org>
Subject: Re: Clarification regd. native-search-paths and search-paths
Date: Sun, 06 Oct 2024 22:58:57 -0400 [thread overview]
Message-ID: <87wmik7h5a.fsf@gmail.com> (raw)
In-Reply-To: <877cakyb29.fsf@lease-up.com> (Felix Lechner's message of "Sun, 06 Oct 2024 18:08:14 -0700")
Hi Felix,
Felix Lechner <felix.lechner@lease-up.com> writes:
>> does use here mean being an "input" to a package?
>
> Yes, precisely. Or being used in a profile.
I see. Thank you.
>> At least for certain variables such as $SSL_CERT_DIR and $SSL_CERT_FILE
>> they only have the desired effect when added to native-search-paths.
>
> Did you also move the input that provides the TLS certificates away from
> native when you tried?
Ah, I think not. I think I see now what Rutherther (on IRC) meant when
they said that guix shell adds to native-inputs.
The input that provided the TLS certificates in my case was nss-certs.
I provided it by adding it to a profile which I then loaded via guix
shell. It seems this adds it to "native"?
> P.S. I'm a Guix learner who likes to help. Please don't trust anything
> I write.
Heh, ditto. While the disclaimer wasn't strictly necessary, I
appreciate your clarification.
--
Suhail
next prev parent reply other threads:[~2024-10-07 2:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-05 18:19 Clarification regd. native-search-paths and search-paths Suhail Singh
2024-10-06 17:49 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-10-06 22:00 ` Suhail Singh
2024-10-07 1:08 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-10-07 2:58 ` Suhail Singh [this message]
2024-10-07 19:03 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-10-07 20:50 ` Suhail Singh
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=87wmik7h5a.fsf@gmail.com \
--to=suhailsingh247@gmail.com \
--cc=felix.lechner@lease-up.com \
--cc=guix-devel@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.