From owner-cvs-all@FreeBSD.ORG Fri Mar 2 19:41:17 2012 Return-Path: Delivered-To: cvs-all@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 120E4106567A; Fri, 2 Mar 2012 19:41:17 +0000 (UTC) (envelope-from flo@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E986C8FC08; Fri, 2 Mar 2012 19:41:16 +0000 (UTC) Received: from nibbler-wlan.fritz.box (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q22JfF0b092016; Fri, 2 Mar 2012 19:41:15 GMT (envelope-from flo@FreeBSD.org) Message-ID: <4F51225A.7000408@FreeBSD.org> Date: Fri, 02 Mar 2012 20:41:14 +0100 From: Florian Smeets User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120222 Thunderbird/11.0 MIME-Version: 1.0 To: Doug Barton References: <201202272335.q1RNZBJc081428@repoman.freebsd.org> <4F508F9C.5040505@FreeBSD.org> <4F5090E2.7000604@freebsd.org> <4F509166.2010509@FreeBSD.org> In-Reply-To: <4F509166.2010509@FreeBSD.org> X-Enigmail-Version: 1.4a1pre Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigCAB05A033ADF43943CCA3297" Cc: cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/security/ca_root_nss Makefile X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: **OBSOLETE** CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2012 19:41:17 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigCAB05A033ADF43943CCA3297 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 02.03.12 10:22, Doug Barton wrote: > On 03/02/2012 01:20, Florian Smeets wrote: >> 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? >=20 > If the user chooses that option, the port should own the link. Having > the link point to a stale location is infinitely more likely than the > user choosing that option but not intending it to actually happen. >=20 I thought a bit more about it, as we delete the link on deinstall anyway there is no reason not to just overwrite it on install, in the rare event that it should exists. Florian --------------enigCAB05A033ADF43943CCA3297 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAk9RIlsACgkQapo8P8lCvwnuJQCeI0r87iVayD/zQzgzCLt3mHjr 0ToAmgKHnJeA7lCPkzvxssbhxAHeLyeV =10QH -----END PGP SIGNATURE----- --------------enigCAB05A033ADF43943CCA3297--