From owner-svn-src-all@FreeBSD.ORG Fri Dec 21 12:31:27 2012 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9843D6D5 for ; Fri, 21 Dec 2012 12:31:27 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.31.39]) by mx1.freebsd.org (Postfix) with ESMTP id 201898FC13 for ; Fri, 21 Dec 2012 12:31:27 +0000 (UTC) Received: from [78.35.147.221] (helo=fabiankeil.de) by smtprelay01.ispgateway.de with esmtpsa (SSLv3:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1Tm1gS-0006ts-Oo for svn-src-all@freebsd.org; Fri, 21 Dec 2012 13:26:36 +0100 Date: Fri, 21 Dec 2012 13:23:03 +0100 From: Fabian Keil To: svn-src-all@freebsd.org Subject: Re: svn commit: r243554 - in head/usr.sbin/pkg_install: add create delete info lib updating version Message-ID: <20121221132303.124765b7@fabiankeil.de> In-Reply-To: References: <201211260511.qAQ5B7DQ002346@svn.freebsd.org> <20121128170032.730be5fab68dba2a09aaa14e@FreeBSD.org> <20121128183422.714562856f27371c95d2a84e@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/oaj8yDwZ6z9F8IHXwzTWZ_d"; protocol="application/pgp-signature" X-Df-Sender: Nzc1MDY3 X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Dec 2012 12:31:27 -0000 --Sig_/oaj8yDwZ6z9F8IHXwzTWZ_d Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Eitan Adler wrote: > On 28 November 2012 21:34, Stanislav Sedov wrote: > > I don't really see how this > > message being in pkg_ tools helps to prevent a possible foot-shooting > > at all. >=20 > It reminds people that using the pkg_* tools once a conversion is done is= wrong. I don't see how that prevents foot-shooting either. Is there a single case where running one of the pkg_* tools is dangerous and spamming the console somehow mitigates this? How is the following helpful?: # pkg2ng pkg_info: You appear to be using the newer pkg(1) tool on this system for p= ackage management, rather than the legacy package management tools (pkg_*).= The legacy tools should no longer be used on this system. Creating backup pkg_info(1) database directory in /var/db/pkg.bak. pkg_info: You appear to be using the newer pkg(1) tool on this system for p= ackage management, rather than the legacy package management tools (pkg_*).= The legacy tools should no longer be used on this system. pkg_info: You appear to be using the newer pkg(1) tool on this system for p= ackage management, rather than the legacy package management tools (pkg_*).= The legacy tools should no longer be used on this system. pkg_info: You appear to be using the newer pkg(1) tool on this system for p= ackage management, rather than the legacy package management tools (pkg_*).= The legacy tools should no longer be used on this system. Installing adns-1.4_1... done pkg_info: You appear to be using the newer pkg(1) tool on this system for p= ackage management, rather than the legacy package management tools (pkg_*).= The legacy tools should no longer be used on this system. pkg_info: You appear to be using the newer pkg(1) tool on this system for p= ackage management, rather than the legacy package management tools (pkg_*).= The legacy tools should no longer be used on this system. pkg_info: You appear to be using the newer pkg(1) tool on this system for p= ackage management, rather than the legacy package management tools (pkg_*).= The legacy tools should no longer be used on this system. pkg_info: You appear to be using the newer pkg(1) tool on this system for p= ackage management, rather than the legacy package management tools (pkg_*).= The legacy tools should no longer be used on this system. pkg_info: You appear to be using the newer pkg(1) tool on this system for p= ackage management, rather than the legacy package management tools (pkg_*).= The legacy tools should no longer be used on this system. pkg_info: You appear to be using the newer pkg(1) tool on this system for p= ackage management, rather than the legacy package management tools (pkg_*).= The legacy tools should no longer be used on this system. Installing autoconf-2.68... done [...] =20 > > At very least, it makes sense to make it conditional on WITH_PKGNG, so = this > > code does not end up compiled in if PKGNG is disabled in src.conf. >=20 > Interesting idea. Maybe I shall do this. Yes, please.=20 Fabian --Sig_/oaj8yDwZ6z9F8IHXwzTWZ_d Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlDUVKoACgkQBYqIVf93VJ0V7gCgqkVWtx+PwPARlXdYlh+upqVr ZGEAnixtfHAVrQjmYgHeHjn60Ohh2GmL =KcI+ -----END PGP SIGNATURE----- --Sig_/oaj8yDwZ6z9F8IHXwzTWZ_d--