unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Prikler <leo.prikler@student.tugraz.at>
To: Raghav Gururajan <rg@raghavgururajan.name>
Cc: guix-devel@gnu.org
Subject: Re: [DOUBT]: native-search-paths VS search-paths
Date: Tue, 09 Feb 2021 11:06:35 +0100	[thread overview]
Message-ID: <726a227171fefad2ccd1240221d22c87da8657c5.camel@student.tugraz.at> (raw)
In-Reply-To: <c1dbcb70-eac2-2c88-50a9-6ae2c1c38e4d@raghavgururajan.name>

Am Dienstag, den 09.02.2021, 04:56 -0500 schrieb Raghav Gururajan:
> Hi Leo!
> 
> > Both search-paths and native-search-paths are expanded in a build
> > environment to form an environment variable.  search-paths works on
> > inputs whereas native-search-paths works on native-inputs.  In
> > addition, native-search-paths also end up in your
> > $GUIX_PROFILE/etc/profile.
> 
> So it is like how "PATH" is established inside build environment?
> 
> Also, are they useful only to the package itself or to other
> packages 
> that depend on it as well?
Depends on the package.  If it gets propagated into the build
environment, the variable is set as well.  At other times, it might be
set through the wrap phase for runtime purposes.

Regards,
Leo



  reply	other threads:[~2021-02-09 10:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-09  9:32 [DOUBT]: native-search-paths VS search-paths Leo Prikler
2021-02-09  9:56 ` Raghav Gururajan
2021-02-09 10:06   ` Leo Prikler [this message]
2021-02-09 10:15     ` Raghav Gururajan
2021-02-09 10:22     ` Hartmut Goebel
2021-02-09 12:26       ` Leo Prikler
  -- strict thread matches above, loose matches on Subject: below --
2021-02-09  8:58 Raghav Gururajan

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=726a227171fefad2ccd1240221d22c87da8657c5.camel@student.tugraz.at \
    --to=leo.prikler@student.tugraz.at \
    --cc=guix-devel@gnu.org \
    --cc=rg@raghavgururajan.name \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).