FreeBSD ports tree https://cgit-dev.freebsd.org/ports/atom?h=release%2F12.3.0 2021-07-14T16:15:03Z 2021-07-14T16:15:03Z Po-Chuan Hsieh sunpoet@FreeBSD.org 2021-07-14T16:06:05Z urn:sha1:fcb34faf706733a667358b293970fac444251828 It helps avoid generating wrong patches, e.g. patch-grpc.gemspec in r567838 [1]. from diff manpage: -a --text Treat all files as ASCII text. Normally diff will simply print "Binary files ... differ" if files contain binary characters. Use of this option forces diff to produce a diff. [1] https://cgit.FreeBSD.org/ports/diff/net/rubygem-grpc130/files/patch-grpc.gemspec?id=073c1c710a0c7254820adab9920c1903ace83fae PR: 257027 Approved by: mat (portmgr) 2021-04-06T14:27:10Z Mathieu Arnold mat@FreeBSD.org 2021-04-06T11:32:08Z urn:sha1:5d33e045968104ac678d8b4b4ec1e8956bbf68e0 Where appropriate fiddle with a few other things. 2020-11-11T13:29:52Z Mathieu Arnold mat@FreeBSD.org 2020-11-11T13:29:52Z urn:sha1:f916081e1cf3cf8f63d7d2e708353f6a9303401c set pipefail changes the pipeline return status from being the return status of the last command to the last non 0 exit status of any command in the pipeline. This is needed to make sure all the commands in a pipeline did actually return a non 0 status and not only the last one. PR: 250723 Exp-run by: antoine Reviewed by: bapt Approved by: bapt Differential Revision: https://reviews.freebsd.org/D27007 2020-11-05T16:51:30Z Mathieu Arnold mat@FreeBSD.org 2020-11-05T16:51:30Z urn:sha1:aeda355b1b6ff45a38b6fb053ccebe1f1ba2995e 2020-11-05T16:42:35Z Mathieu Arnold mat@FreeBSD.org 2020-11-05T16:42:35Z urn:sha1:e9b2078c6cc6d9d66ee4624024372db93a296921 set pipefail changes the pipeline return status from being the return status of the last command to the last non 0 exit status of any command in the pipeline. This is needed to make sure all the commands in a pipeline did actually return a non 0 status and not only the last one. 2020-01-23T08:55:25Z Mathieu Arnold mat@FreeBSD.org 2020-01-23T08:55:25Z urn:sha1:f5e4ea9e146c6e47042ed9df41e9f65f02eb0931 The glob in `find ./*` is handled by the shell and actually sorts the files, so one needs to to ask find to sort the result, using `find -s`. `find ./* -maxdepth 0` is not equivalent to `find . -maxdepth 0`, the depth increases by one as `./x` is on level deeper than `.`. Pointy hat: bdrewery 2020-01-21T20:36:14Z Bryan Drewery bdrewery@FreeBSD.org 2020-01-21T20:36:14Z urn:sha1:ed09885fec597eb62cafff8e5505b7fd558cf8a9 This change also avoids cmdline length errors and other subst parsing issues that were previously targeted. Sponsored by: DellEMC 2019-05-20T13:04:03Z Mathieu Arnold mat@FreeBSD.org 2019-05-20T13:04:03Z urn:sha1:7551edfa4ba6b8daef881b933b2cd535d510eb19 This will reduce the churn when base system diff subtly changes what is put in that field. 2018-06-08T09:26:41Z Mathieu Arnold mat@FreeBSD.org 2018-06-08T09:26:41Z urn:sha1:b19fe1e937f9ad207c85f935169d19e282adcb5d You have a single quoted string containing a backslash followed by a linefeed (newline). Unlike double quotes or unquoted strings, this has no special meaning. The string will contain a literal backslash and a linefeed. If you wanted to break the line but not add a linefeed to the string, stop the single quote, break the line, and reopen it. PR: 227109 Submitted by: mat Sponsored by: Absolight 2018-06-08T09:26:38Z Mathieu Arnold mat@FreeBSD.org 2018-06-08T09:26:38Z urn:sha1:49b7fa03acb4c78015afd4f0fbd62791e2b10e50 Since files and arguments are strings passed the same way, programs can't properly determine which is which, and rely on dashes to determine what's what. A file named -f (touch -- -f) will not be deleted by the problematic code. It will instead be interpreted as a command line option, and rm will even report success. Using ./* will instead cause the glob to be expanded into ./-f, which no program will treat as an option. It is not possible to use `-f *` because -f only forces the next argument to be a directory, a later directory named -delete would mess things up. PR: 227109 Submitted by: mat Sponsored by: Absolight