All
Enclosed are the minutes from yesterday’s call
regards
Andrew
-------------------------
Minutes of the 27th October 2022 Teleconference Austin-1266 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 28th October 2022
Attendees:
Don Cragun, IEEE PASC OR
Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR
Eric Ackermann, HPI, University of Potsdam
Geoff Clare, The Open Group
Andrew Josey, The Open Group
Tom Thompson, IEEE
Apologies:
Mark Ziegast
Eric Blake, Red Hat, The Open Group OR
* General news
A reminder that the calls next week are one hour earlier in Europe
due to the end of Summer time!
This was a call dedicated to general bugs.
* Carried Forward
This section trimmed -- see Austin/1264
* Current Business
Bug 1600: Problems with the suggested single-line shell script: $0
"$@" Accepted as marked https://austingroupbugs.net/view.php?id=1600
This item is tagged for Issue 8.
Change:
However, all of the standard utilities, including the regular
built-ins but not the special built-ins described in [xref to
2.14], shall be implemented in a manner ...
to:
However, all of the standard utilities other than:
The special built-ins described in [xref to 2.14] The
intrinsic utilities named in [xref to Table 1-5], except
for kill
shall be implemented, regardless of whether they are also
implemented as regular built-ins, in a manner ...
On page 3615 line 124885-124906 section C.1.7, change:
All of the regular built-in utilities [...] These arguments
were ultimately the most effective.
to:
Earlier versions of this standard required that all of the
regular built-in utilities, including intrinsic utilities, could
be exec-ed. This was always a contentious requirement, and with
the introduction of intrinsic utilities the standard developers
decided to exempt the utilities that this standard requires to
be intrinsic, with the exception of kill. The kill utility is
still genuinely useful when exec-ed, only lacking support for
the % job ID notation, whereas examples given of uses for the
other utilities that are now exempted were considered contrived
(such as using cd to test accessibility of a directory, which
can be done using test -x). If an application needs exec-able
versions of some of the exempted intrinsic utilities, it can
easily provide them itself, on systems that support the
(non-standard but ubiquitous) "#!" mechanism to make scripts
executable by the exec family of functions, as links to a
two-line shell script:
#! /path/to/sh
${0##*/} "$@"
Bug 1599: Unspecified behaviour for "strings -" too narrow Accepted
https://austingroupbugs.net/view.php?id=1599
This item is tagged for TC3-2008.
Bug 1598: putenv should be allowed to fail with EINVAL Accepted as Marked
https://austingroupbugs.net/view.php?id=1598
This item is tagged for TC3-2008.
On page 1751 line 56642 section putenv(), change:
The putenv() function shall use the string argument to set
environment variable values. The string argument should point
to a string of the form "name=value". The putenv() function
shall make the value of the environment variable name equal to
value by altering an existing variable or creating a new one.
In either case, the string pointed to by string shall become
part of the environment, so altering the string shall change
the environment.
to:
The putenv() function shall use the string argument to set, or
optionally unset, an environment variable value:
If the string argument points to a string of the form
"name=value", where name is a valid name, the putenv()
function shall make the value of the environment variable
with that name equal to value by altering an existing
variable or creating a new one. In either case, the string
pointed to by string shall become part of the environment,
so altering the string shall change the environment.
If the string argument points to a string containing a valid
name, the putenv() function shall either remove the environment
variable with that name (if it exists) from the environment
or fail with errno set to [EINVAL].
Otherwise, the behavior is unspecified.
After page 1751 line 56652 section putenv(), add:
[EINVAL]
The string argument points to a string that is not of the
form "name=value", where name is a valid name.
Bug 1597: clockid_t are not usable with the clock() function and the text
should say clock*() functions. Accepted
https://austingroupbugs.net/view.php?id=1597
This item is tagged for TC3-2008.
Bug 1596: Not one, but three expansions may create multiple fields from a
single word Dup of 1193
https://austingroupbugs.net/view.php?id=1596
Closed, duplicate of 1193.
Bug 1593: specify whether struct sockaddr_un.sun_path can be a flexible array
member OPEN
https://austingroupbugs.net/view.php?id=1593
Wait for Eric to complete his action on bug 561
Bug 1592: Add %n$ support to the printf utility Accepted
https://austingroupbugs.net/view.php?id=1592
This item is tagged for Issue 8.
Next time we will start on Bug 1591.
Next Steps
----------
The next calls are on:
Mon 2022-10-31 (general bugs)
Thu 2022-11-03 (general bugs)
The calls are for 90 minutes
Apologies in advance:
Eric Blake: 2022-11-03
Calls are anchored on US time. (8am Pacific)
Please check the calendar invites for dial in details.
Bugs are at:
https://austingroupbugs.net
An etherpad is usually up for the meeting, with a URL using the date format as
below:
https://posix.rhansen.org/p/20xx-mm-dd
(For write access this uses The Open Group single sign on,
for those individuals with gitlab.opengroup.org accounts.
Please contact Andrew if you need to be setup)
--------
Andrew Josey The Open Group
Austin Group Chair
Email: a.jo...@opengroup.org
Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England
To learn how we maintain your privacy, please review The Open Group Privacy
Statement at http://www.opengroup.org/privacy.
To unsubscribe/opt-out from this mailing list login to The Open Group
collaboration portal at
https://collaboration.opengroup.org/operational/portal.php?action=unsub&listid=2481
