On 4/7/23 12:48, mh@mike.franken.de wrote:
On Donnerstag, 6. April 2023 23:05:33 CEST Bernhard Voelker wrote:
On 4/5/23 23:16, mh@mike.franken.de wrote:
On Montag, 3. April 2023 12:00:22 CEST Dominique Leuenberger wrote: This might break lots of Makefiles and other scripts.
I don't see why would this break many Makefiles. Usually they're not using -n, but rather either nothing or -f, don't they?
Using -f forces overwriting existing files, -n should preserve them, if they exist.
Sure, but I wouldn't know a place in Makefiles where the latter would be used. It would look a bit strange to me just to avoid the double writing of the destination file if various targets would copy the same content from different places to it. Otherwise, if the Makefile would instruct to copy the same file again and again (with or without overwriting), then this would be strange either. Finally, if the content of the source files was different, then I'd call it even a bit fishy for a build process to copy just the first one. I don't say that -n is not useful in general or not used in scripts or interactively, but probably very seldom in Makefiles ... and if so, then that option could probably just be removed there. Have a nice day, Berny