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: guix-devel@gnu.org
Subject: Re: environment variable handling cleanup ?
Date: Mon, 23 Mar 2020 09:54:57 +0100	[thread overview]
Message-ID: <f674c83e-84a1-27b9-4ac3-d66285dcb9bd@crazy-compilers.com> (raw)
In-Reply-To: <CAEwRq=o2SvRPNU+QJMNA2T=g_Yzjf9m38FFY+CfSdJzFZdg4_g@mail.gmail.com>

Am 22.03.20 um 15:40 schrieb Vincent Legoll:
> as I'm trying to ramp up my scheme & guix -fu, I'm wondering if
> something along the lines of :

Well, I did not count how often this is used, but (guix built utils
update-env) might benefit from this, to.


> There's also the added (or (getenv ...) "") which is not present in
> all target cases.

I suggest to default the value to #f (False), since - depending on the
variables semantic - it may make a difference whether the variabel is
empty or actually unset. This is especially true when used within a
programming language like Scheme which has a notion of "False" - which
env-vars do not have.


> Another question is the usefulness of the separator parameter,
> as I think all target cases use ":", so hardcoding it would be a
> sensible choice.

I doubt there Is a need for different separators The path separator is
defined to be ":" in Posix. So I'd suggest to use a hardcoded value.

-- 

Regards
Hartmut Goebel

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

  reply	other threads:[~2020-03-23  8:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-22 14:40 environment variable handling cleanup ? Vincent Legoll
2020-03-23  8:54 ` Hartmut Goebel [this message]
2020-03-28  8:06   ` Vincent Legoll

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=f674c83e-84a1-27b9-4ac3-d66285dcb9bd@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.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.