GNU bug report logs - #20713
aclocal/tar.m4 and solaris 5.10 where `id -u` is not supported

Previous Next

Package: automake;

Reported by: Karl Berry <karl <at> freefriends.org>

Date: Mon, 1 Jun 2015 21:03:02 UTC

Severity: normal

Tags: confirmed

Done: Mike Frysinger <vapier <at> gentoo.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Karl Berry <karl <at> freefriends.org>
To: vapier <at> gentoo.org
Cc: 20713 <at> debbugs.gnu.org
Subject: bug#20713: aclocal/tar.m4 and solaris 5.10
Date: Mon, 21 Feb 2022 16:26:34 -0700
    should we change "unknown" to $GID & $UID respectively ?

I guess it couldn't hurt, although I doubt it makes any difference in
practice.

    if test $am_uid = "unknown"; then

Don't we usually avoid quoting constant strings? I.e.:
if test "$am_uid" = unknown; then

      AC_MSG_WARN([ancient id detected; assuming current UID is ok, but dist-ustar might not work])

"Might"? Either it works or it doesn't? Anyway, who ever uses ustar?
Never seen it.

Anyway, seems like such a warning "might" be useful when producing an
archive with automake (running make dist), but not when running
configure. When merely doing "./configure && make", ustar is irrelevant.

Anyway #2, I think the chances of someone wanting to produce a ustar
archive on a system with old id is zero.

Thus I suggest just fixing the syntax stuff and letting it go at that. 

    the point of the checks isn't just to annoy the user.

No :)? That's what it seems like. Helpful to the package developer;
annoyance to the configure user. -k




This bug report was last modified 3 years and 128 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.