[bug #27146] cp --no-preserve=mode is counter-intuitive

[Matt McCutchen]

Follow-up Comment #1, bug #27146 (project coreutils):

I agree with this argument
<http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=488024#15> that
--no-preserve=mode is merely the opposite of --preserve=mode and should not
activate completely new behavior.

Regarding the default behavior of cp, I agree heartily that the current,
historical behavior is nearly useless and simply applying the destination
default permissions (umask or default ACL) would be much better. 
Nevertheless, the historical behavior has stood for a long time and been
adopted by tar and rsync, and while I personally would be happy to change the
behavior of all of those tools on my system and see what breaks, I highly
doubt the maintainers would want to do that to everyone.  *sigh*  So instead,
let's seek a new option to use the destination default permissions and ignore
the source permissions.

This issue is quite dear to me.  I originally raised it on the bug-tar list
<http://lists.gnu.org/archive/html/bug-tar/2005-07/msg00016.html> in 2005. 
Ultimately, it drove me completely away from GNU cp in favor of rsync, where I
popularized the --chmod=ugo=rwX combination (see this commit to the man page
<http://gitweb.samba.org/?p=rsync.git;a=commitdiff;h=77ed253c73f5a215014a50e6f9c9f81b8b3b4c42>)
and implemented support for default ACLs to go along with it.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?27146>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/