In the past if you did:
cp --no-clobber $in $out
And "out" existed, "cp" exited with 0. But now, with coreutils 9.2, it
exists with 1.
Is this on purpose?
(When replying include my email in the field "to", as I'm not subscribed to
this list)
https://youtu.be/o_kh1_gOkwk
On Fri, 31 Mar 2023 at 22:01, Paul Eggert wrote:
> On 2023-03-31 10:01, Alberto Salvia Novella wrote:
> > Is this on purpose?
>
> Yes, part of the idea was to let shell programmers easily test whether
> cp successfully copied the data. Having cp -
I get the impression that right now --no-clover is optimized for the less
common scenarios, while making it less useful for the common ones.
Also --update isn't a substitute of --no-clover. As --no-clover is for
copying when the file is missing, not when it isn't updated.
For example imagine that
Or use:
cp --no-clover $in $out || true
But again, surprising behavior. Just a new special case to memorize.
On Sat, 1 Apr 2023 at 03:36, Alberto Salvia Novella
wrote:
> I get the impression that right now --no-clover is optimized for the less
> common scenarios, while making it less
eless. Nobody should be using it.
On Sat, 1 Apr 2023 at 03:41, Alberto Salvia Novella
wrote:
> Or use:
> cp --no-clover $in $out || true
>
> But again, surprising behavior. Just a new special case to memorize.
>
> On Sat, 1 Apr 2023 at 03:36, Alberto Salvia Novella
> wrote:
>
Maybe simpler:
-m --missing
Only copy non existing files.
On Sat, 1 Apr 2023 at 17:44, Pádraig Brady wrote:
> On 01/04/2023 00:29, Paul Eggert wrote:
> > On 2023-03-31 14:32, Pádraig Brady wrote:
> >
> >> Perhaps we should support:
> >> --no-clobber[={skip, fail (default)}]
> >>
> >> so the
