On 31/03/2023 07:27, A. Wilcox wrote:
On Mar 30, 2023, at 9:48 AM, Pádraig Brady wrote:
On 30/03/2023 09:20, A. Wilcox wrote:
Hello,
While updating coreutils to 9.2 on Adélie Linux, I’ve run into a few
interesting corner-cases in the test suite. As a note, our distribution
is using musl as t
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)
Alberto Salvia Novella writes:
> 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)
We
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 conform to POSIX was a
lesser consideration, though it's a bit nicer if -n and -i are somewhat
consisten
On 2023-03-31 13:01 -0700, 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.
By making them stop using the '-n' option, since they cannot rely
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 conform to POSIX w
On 2023-03-31 13:37, Sven Joachim wrote:
On 2023-03-31 13:01 -0700, Paul Eggert wrote:
part of the idea was to let shell programmers easily test whether
cp successfully copied the data.
By making them stop using the '-n' option, since they cannot rely on the
exit code anyway?
Portable code
On 31/03/2023 22:15, Paul Eggert wrote:
On 2023-03-31 13:37, Sven Joachim wrote:
On 2023-03-31 13:01 -0700, Paul Eggert wrote:
part of the idea was to let shell programmers easily test whether
cp successfully copied the data.
By making them stop using the '-n' option, since they cannot rely
On 2023-03-31 14:32, Pádraig Brady wrote:
Perhaps we should support:
--no-clobber[={skip, fail (default)}]
so then users can at least easily change -n to --no-clobber=skip
to get the old behavior?
An alternative would be to augment the --update option to support:
--update[={none, older (
In principle I have no strong opinion on what the behaviour should be.
But if one strictly follows the POSIX wording:
>The following exit values shall be returned:
> 0
>All input files were [copied/moved] successfully.
>>0
>An error occurred.
The change seems to make
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 useful for
12 matches
Mail list logo
