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

[Mark Tiefenbruck]

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

I've modified cp on my system based on a patch found here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=488024

The problem was (besides that it didn't apply anymore for trivial reasons)
that it set the execute bits on every file. I've made it so that it only sets
the execute bits that were set in the source file but otherwise complies with
the umask.

I understand this may not be desirable for some use cases, since the
annoyance is that certain filesystems set the execute bits on every file. I
also understand that the coreutils devs are never going to make the
--no-preserve=mode option do something reasonable due to POSIX. I would
suggest adding a new option in order to provide this behavior, as well as some
control over execute bits.

(file #19587)
    _______________________________________________________

Additional Item Attachment:

File name: coreutils-fix-no-preserve-mode.diff Size:0 KB


    _______________________________________________________

Reply to this item at:

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

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