Date: Tue, 24 Jan 2006 22:12:37 +0300 From: "Andrew P." <infofarmer@gmail.com> To: Scot Hetzel <swhetzel@gmail.com> Cc: FreeBSD Ports <ports@freebsd.org> Subject: Re: cp -n vs. test -f Message-ID: <cb5206420601241112v2786c4ccg3b5bd6837f4e79d0@mail.gmail.com> In-Reply-To: <790a9fff0601241026s3f4e7f09k92ab1de2cd974b5d@mail.gmail.com> References: <cb5206420601240941r16ad7ed7x8ab50c40fee86e2b@mail.gmail.com> <790a9fff0601241026s3f4e7f09k92ab1de2cd974b5d@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/24/06, Scot Hetzel <swhetzel@gmail.com> wrote: > On 1/24/06, Andrew P. <infofarmer@gmail.com> wrote: > > So why do we use "if [ ! -f file ] ; then cp file.new file; fi" > > instead of "cp -n file.new file" in pkg-plist's and many > > other places? I think the "cp -n" way is what we really > > mean to do. > > > We probably don't use it because of the following at the bottom of the > cp man page. > > "The -v and -n options are non-standard and their use in scripts is > not recommended." > > Scot > -- > DISCLAIMER: > No electrons were mamed while sending this message. Only slightly bruised= . > cp manpage has this since FreeBSD 4.7-RELEASE, can we get over it and start using it?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cb5206420601241112v2786c4ccg3b5bd6837f4e79d0>