From owner-freebsd-ports@FreeBSD.ORG Fri Aug 24 21:57:53 2012 Return-Path: Delivered-To: ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 14679106566B; Fri, 24 Aug 2012 21:57:53 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 4581914DAB9; Fri, 24 Aug 2012 21:57:17 +0000 (UTC) Message-ID: <5037F8BB.9020501@FreeBSD.org> Date: Fri, 24 Aug 2012 14:57:15 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Eitan Adler References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <785B5BAD-E015-4624-B3A1-D05E1BD97E51@freebsd.org> <5AC662AA-4874-4BC2-9862-65518B79B840@freebsd.org> <5036EE2E.4040606@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.3 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org, Steve Wills , Baptiste Daroussin , current@freebsd.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2012 21:57:53 -0000 On 8/23/2012 8:03 PM, Eitan Adler wrote: > On 23 August 2012 22:59, Doug Barton wrote: >> I tend to agree with Steve here ... we can't be responsible for other >> people's poorly written docs. > > This isn't about poorly written docs. This is the user expecting a > tool to exist, which doesn't. Take another example of a sysadmin which > rarely installs new systems, installs FreeBSD for the third time, and > then gets confused when "pkg install vim" fails. Aren't we going to install the pkg package on new systems when they are installed? Isn't that (shouldn't that be?) part of the project plan? It would be insane for us not to do that, at least for the releases where pkg is the default. >> You bring up a valid point that we should >> keep in mind for our own however. The bootstrapping issue will be the >> smallest possible annoyance on a long road of the migration process. > > The bootstrapping issue is a factor even after the migration :) I think that the point I'm trying to make is that it shouldn't be. > note that I'm not talking about the mechanism here, I'm trying to > avoid "pkg doesn't seem to be installed on my fresh system" becoming a > FAQ. The way that we avoid that problem is not to create it for ourselves in the first place. :) The role of pkg-bootstrap is for those users who have already-installed systems that need to do the conversion, or if somehow pkg becomes corrupted on the user's system and needs to be reinstalled. That's it. I like that you're thinking through the related issues, but in this particular case I think you're overthinking it. Doug -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909)