A NOTE has been added to this issue. 
====================================================================== 
https://austingroupbugs.net/view.php?id=1808 
====================================================================== 
Reported By:                cquike
Assigned To:                
====================================================================== 
Project:                    1003.1(2016/18)/Issue7+TC2
Issue ID:                   1808
Category:                   Shell and Utilities
Type:                       Clarification Requested
Severity:                   Editorial
Priority:                   normal
Status:                     Resolved
Name:                       Enrique Garcia 
Organization:                
User Reference:              
Section:                    getconf 
Page Number:                (page or range of pages) 
Line Number:                (Line or range of lines) 
Interp Status:              --- 
Final Accepted Text:        https://austingroupbugs.net/view.php?id=1808#c6747 
Resolution:                 Accepted As Marked
Fixed in Version:           
====================================================================== 
Date Submitted:             2024-02-03 01:44 UTC
Last Modified:              2024-04-19 12:28 UTC
====================================================================== 
Summary:                    Add option -a to getconf utility
====================================================================== 

---------------------------------------------------------------------- 
 (0006768) kre (reporter) - 2024-04-19 12:28
 https://austingroupbugs.net/view.php?id=1808#c6768 
---------------------------------------------------------------------- 
wrt biugnote:6766

   confstr() returns the implementation's standard PATH,

that's fine, but:

   so the value will not contain any newlines,

How does that follow?   What if the implementation's standard PATH
contains the directory whose name is obtained from

   printf '%s\n%s' "/usr/" "POSIX"

as a directory no-one would normally include in PATH, which contains
versions
of various standard utilities to replace the ones the implementation
normally
uses which differ from the standard in some way.

Is there something somewhere which prohibits an implementation like that?
If not, your conclusion doesn't follow. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2024-02-03 01:44 cquike         New Issue                                    
2024-02-03 01:44 cquike         Name                      => Enrique Garcia  
2024-02-03 01:44 cquike         Section                   => getconf         
2024-02-03 01:44 cquike         Page Number               => (page or range of
pages)
2024-02-03 01:44 cquike         Line Number               => (Line or range of
lines)
2024-02-25 05:48 kre            Note Added: 0006674                          
2024-03-06 10:40 cquike         Note Added: 0006705                          
2024-04-11 15:19 geoffclare     Note Added: 0006747                          
2024-04-11 15:21 geoffclare     Note Edited: 0006747                         
2024-04-11 15:21 geoffclare     Interp Status             => ---             
2024-04-11 15:21 geoffclare     Final Accepted Text       =>
https://austingroupbugs.net/view.php?id=1808#c6747    
2024-04-11 15:21 geoffclare     Status                   New => Resolved     
2024-04-11 15:21 geoffclare     Resolution               Open => Accepted As
Marked
2024-04-11 15:22 geoffclare     Tag Attached: issue9                         
2024-04-17 19:27 eblake         Note Added: 0006764                          
2024-04-18 01:04 philip-guentherNote Added: 0006765                          
2024-04-18 09:36 geoffclare     Note Added: 0006766                          
2024-04-19 12:28 kre            Note Added: 0006768                          
======================================================================


  • [1003.1(2016... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
      • Re:... Philip Guenther via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group

Reply via email to