From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 08:44:28 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 87C54106564A; Fri, 24 Aug 2012 08:44:28 +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 56D9C8FC0C; Fri, 24 Aug 2012 08:44:28 +0000 (UTC) Received: from bender.solomo.local (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q7O8iQjb076261; Fri, 24 Aug 2012 08:44:27 GMT (envelope-from flo@freebsd.org) Message-ID: <50373EEA.3080104@freebsd.org> Date: Fri, 24 Aug 2012 10:44:26 +0200 From: Florian Smeets User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120823 Thunderbird/15.0 MIME-Version: 1.0 To: Baptiste Daroussin References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <20120824081543.GB2998@ithaqua.etoilebsd.net> In-Reply-To: <20120824081543.GB2998@ithaqua.etoilebsd.net> X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org, Steve Wills , current@freebsd.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2012 08:44:28 -0000 On 08/24/2012 10:15, Baptiste Daroussin wrote: > On Thu, Aug 23, 2012 at 06:19:57PM -0400, Steve Wills wrote: >> Hi, >> >> It seems to me that renaming the pkg binary in /usr/sbin/pkg to /usr/sbin/pkg-bootstrap would make sense. From a user standpoint, it is confusing that running the command gets different results the second time it is run vs. the first time. I can imagine a user saying "I ran pkg, but it didn't do what they said it would. Now I run it again, and it does do what it is supposed to." Also, it would enable setting up a pkg-bootstrap man page separate from the pkg man page, without confusion about which one you're looking at. >> >> So, opinions? There may still be time to fix it for 9.1 if we can decide quickly. >> >> Thanks, >> Steve >> > > BTW for people who haven't tested and want to share their opinion, here is how > work /usr/sbin/pkg: > > it first checks if ${LOCALBASE}/sbin/pkg is there > - if yes it directly execute ${LOCALBASE}/sbin/pkg with arguments passed to /usr/sbin/pkg > - if no then it will determine you ABI (or take the one in environnement > variable), and fetch the last available pkgng version from http://pkgbeta... > it will extract pkg-static and use it to install pkgng with itself. > on installation is done: it executes ${LOCALBASE}/sbin/pkg with arguments > passed to /usr/sbin/pkg. > > Lots of people having ask in the early days of pkgng for a transparent bootstrap > I have done it that way. > > On of the thing I forgot and kan@ has added is a prompt for the user in case it > is going to bootstrap. > > So that mean that for a normal user, on a fresh vanilla FreeBSD > "pkg install vim-lite" will prompt the user asking if he wants to bootstrap > pkgng, and once bootstraped proceed to the installation of vim-lite > > if pkgng is already there then it will just install vim-lite. > > It was just to clarify, so that anyone understand was this is about. > > I tend to like the bootstrap like it is now (I find it transparent, and straight > forward) but as I said earlier I have no strong opinion on this, so it most > people prefers a separate pkg-bootstrap tools then I'll do it :) Having installed a few 9.1-BETA1 boxes recently, i have to say i absolutely like this behavior, it's totally transparent and you can just start installing packages like you could with pkg_add -r. I don't see the need to introduce an additional step. I actually think the current behavior is user friendly, and renaming it would make it more difficult. If people think the current behavior is misleading we could still clarify the confirmation message. Florian