all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Marius Bakke <mbakke@fastmail.com>, guix-devel <guix-devel@gnu.org>
Subject: Re: How to "tell" a package so extent an environment variable?
Date: Mon, 12 Dec 2016 11:17:09 +0100	[thread overview]
Message-ID: <584E7925.6050603@crazy-compilers.com> (raw)
In-Reply-To: <87d1gymkgx.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>

Am 11.12.2016 um 18:41 schrieb Marius Bakke:
> If PHP can read multiple INI files (which the variable name leads me to

Yes, PHP can read multiple INI files.

> (define-public php
> [...]
>     (native-search-paths
>      (list (search-path-specification
>             (variable "PHP_INI_SCAN_DIR")
>             ;; This might not be the best place to add them.
>             (files '("php/ini")))))
>
> And then, for extensions, they should install an INI file that enables
> them to $out/php/ini. When users install PHP, PHP_INI_SCAN_DIR will be
> pointed towards the users' .guix-profile/php/ini directory.

I assume, the INI files of all extension packages will be linked into
.guix-profile/php/ini. Right? So this would work.

But when building he extension, I'd expect PHP_INI_SCAN_DIR to be set in
/var/tmp/guix-build-….drv-0/environment-variables. But it isn't there.
(For building I would need the header files, not the .ini files, or
course. But this should work the same, shouldn't it?)

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |

      reply	other threads:[~2016-12-12 10:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-11 13:58 How to "tell" a package so extent an environment variable? Hartmut Goebel
2016-12-11 17:41 ` Marius Bakke
2016-12-12 10:17   ` Hartmut Goebel [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=584E7925.6050603@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=guix-devel@gnu.org \
    --cc=mbakke@fastmail.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.