A NOTE has been added to this issue. 
====================================================================== 
https://austingroupbugs.net/view.php?id=1824 
====================================================================== 
Reported By:                dag-erling
Assigned To:                
====================================================================== 
Project:                    Issue 8 drafts
Issue ID:                   1824
Category:                   Shell and Utilities
Type:                       Clarification Requested
Severity:                   Editorial
Priority:                   normal
Status:                     New
Name:                       Dag-Erling Smørgrav 
Organization:                
User Reference:              
Section:                    Utilities 
Page Number:                2741-2748 
Line Number:                90593-90715, 90876-90880 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2024-04-01 15:31 UTC
Last Modified:              2024-04-04 16:59 UTC
====================================================================== 
Summary:                    cp: directories and symlinks
====================================================================== 

---------------------------------------------------------------------- 
 (0006740) geoffclare (manager) - 2024-04-04 16:59
 https://austingroupbugs.net/view.php?id=1824#c6740 
---------------------------------------------------------------------- 
What is there before line 90628 that makes you think its context is
traversal of the source? I'm not seeing it.  Quite the opposite, as line
90613 says "The term source_file refers to the file that is being copied,
whether specified as an operand or a file in a file hierarchy rooted in a
source_file operand."

Lines 90619-90620 say "If none of the options −H, −L, nor −P were
specified, it is unspecified which of −H, −L, or −P will be used as a
default." It doesn't make any sense to try and think of this in terms of it
applying to certain files and not to others. It is simply saying "cp -R a
b" can behave the same as "cp -RH a b", "cp -RL a b", or "cp -RP a b".

You assert that I claimed "the default behavior should be to follow
symbolic links". That is not true.  I said that the pathname resolution
rules require that symbolic links are followed except when a certain set of
conditions is met. For cp, one of those exception conditions is that the -P
option is in effect.  If a cp implementation has -P as the default when
none of -H, -L or -P is specified, then that condition is met by default
and symlinks will not be followed by default. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2024-04-01 15:31 dag-erling     New Issue                                    
2024-04-01 15:31 dag-erling     Name                      => Dag-Erling
Smørgrav
2024-04-01 15:31 dag-erling     Section                   => Utilities       
2024-04-01 15:31 dag-erling     Page Number               => 2741-2748       
2024-04-01 15:31 dag-erling     Line Number               => 90593-90715,
90876-90880
2024-04-02 06:19 dannyniu       Note Added: 0006731                          
2024-04-02 06:20 dannyniu       Note Added: 0006732                          
2024-04-02 06:21 dannyniu       Note Deleted: 0006732                        
2024-04-02 06:22 dannyniu       Note Edited: 0006731                         
2024-04-02 15:51 geoffclare     Note Added: 0006734                          
2024-04-04 14:30 geoffclare     Note Added: 0006737                          
2024-04-04 16:01 dag-erling     Note Added: 0006739                          
2024-04-04 16:59 geoffclare     Note Added: 0006740                          
======================================================================


  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group

Reply via email to