From: ludo@gnu.org (Ludovic Courtès)
To: John Darrington <john@darrington.wattle.id.au>
Cc: 23112@debbugs.gnu.org
Subject: bug#23112: value of _CS_PATH\
Date: Tue, 03 May 2016 22:22:43 +0200 [thread overview]
Message-ID: <87bn4mki24.fsf@gnu.org> (raw)
In-Reply-To: <87bn5nwxmx.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 05 Apr 2016 23:31:34 +0200")
ludo@gnu.org (Ludovic Courtès) skribis:
> John Darrington <john@darrington.wattle.id.au> skribis:
>
>> Would it not be correct for guix to have
>>
>> confstr (_CS_PATH, buf, len);
>>
>> set the contents of buf with the bin directory of the currently
>> installed coreutils package?
>>
>> For me, it returns /bin:/usr/bin which is not correct.
>
> Fixing it is a bit tricky because:
>
> 1. The meaning of this variable is ill-defined. Specifically, POSIX
> says it “is the value for the PATH environment variable that finds
> all standard utilities.” By “standard utilities”, surely they must
> be talking of ‘guile’, ‘guix’, ‘herd’, and a couple of others, but
> we can’t be sure. ;-)
>
> http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/unistd.h.html
>
> 2. If CS_PATH refers to Coreutils, then that means that libc refers to
> Coreutils, which is inconvenient at best.
>
> 3. We could set CS_PATH to /run/current-system/profile/bin but that
> wouldn’t work on foreign distros.
>
> So I’m inclined to leave things as is.
I’ll close the bug if you don’t mind, but…
> Did you find a situation where the invalid value was causing troubles?
… I’m still interested in knowing this. :-)
TIA,
Ludo’.
next prev parent reply other threads:[~2016-05-03 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 18:06 bug#23112: value of _CS_PATH\ John Darrington
2016-04-05 21:31 ` Ludovic Courtès
2016-05-03 20:22 ` Ludovic Courtès [this message]
2016-05-04 5:45 ` John Darrington
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=87bn4mki24.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=23112@debbugs.gnu.org \
--cc=john@darrington.wattle.id.au \
/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).