On Thu, 02 Feb 2023 16:44:05 -0800, David Levine writes:
>Anyways, I'd like to keep the 1.7
>behavior for 1.8 and change it after.  Can we agree to that?

minor data point: after following the discussion here, i've decided
that for now _the debian packages_ of nmh should not distinguish
between unset $HOME and set-but-empty $HOME, and that either should cause a
fallback to getpw*.

(1.8RC2 will hopefully/likely be part of the upcoming debian
release; the previous release shipped with 1.7.1.)

regards
az

Description: treat set-but-empty $HOME same as unset
 upstream code aborts on empty $HOME and falls back to getpw* only on unset $HOME,
 which is undesirable (affects xlbiff's testsuite and generally surprises end users).
 this patch makes it fall back for both empty and unset $HOME.
Author: Alexander Zangerl <[email protected]>
Bug: https://bugs.debian.org/1029752
Last-Update: 2023-02-02
--- a/sbr/path.c
+++ b/sbr/path.c
@@ -38,10 +38,7 @@ void
 set_mypath(void)
 {
     char *var = getenv("HOME");
-    if (var) {
-        if (!*var)
-            die("environment variable HOME is empty");
-
+    if (var && *var) {
         mypath = mh_xstrdup(var);
         return;
     }
-- 
Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + https://snafu.priv.at/
He who joyfully marches to music in rank and file has already earned my 
contempt. He has been given a large brain by mistake, since for him the 
spinal cord would fully suffice. -- Einstein

Attachment: signature.asc
Description: Digital Signature

Reply via email to