Date: Fri, 02 Mar 2012 10:20:34 +0100 From: Florian Smeets <flo@freebsd.org> To: Doug Barton <dougb@freebsd.org> Cc: cvs-ports@freebsd.org, cvs-all@freebsd.org, ports-committers@freebsd.org Subject: Re: cvs commit: ports/security/ca_root_nss Makefile Message-ID: <4F5090E2.7000604@freebsd.org> In-Reply-To: <4F508F9C.5040505@FreeBSD.org> References: <201202272335.q1RNZBJc081428@repoman.freebsd.org> <4F508F9C.5040505@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02.03.2012 10:15, Doug Barton wrote:
> Would '${LN} -sf' have been a safer choice?
Why safer? What if someone has a link pointing to another cert file?
${LN} -sf would just overwrite it. Now we only create the link if it's
not there. IMHO the safest choice for all cases, no?
Florian
>
>
> On 02/27/2012 15:35, Florian Smeets wrote:
>> flo 2012-02-27 23:35:11 UTC
>>
>> FreeBSD ports repository
>>
>> Modified files:
>> security/ca_root_nss Makefile
>> Log:
>> make sure installation does not fail if for whatever reason the symlink in
>> /etc/ssl is still there on (re)install phase with ETCSYMLINK option set.
>>
>> Submitted by: mi
>>
>> Revision Changes Path
>> 1.19 +2 -1 ports/security/ca_root_nss/Makefile
>>
>> http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/security/ca_root_nss/Makefile.diff?&r1=1.18&r2=1.19&f=u
>>
>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F5090E2.7000604>