From owner-freebsd-current@freebsd.org Tue Mar 15 15:21:39 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6EE0CAD1342; Tue, 15 Mar 2016 15:21:39 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 33A4F1206; Tue, 15 Mar 2016 15:21:39 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from [10.9.9.241] (helo=rmm6prod02.runbox.com) by bars.runbox.com with esmtp (Exim 4.71) (envelope-from ) id 1afpyb-00072p-8d; Tue, 15 Mar 2016 15:29:37 +0100 Received: from mail by rmm6prod02.runbox.com with local (Exim 4.76) (envelope-from ) id 1afpyb-0006I9-7i; Tue, 15 Mar 2016 15:29:37 +0100 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [Authenticated user (846156)] by runbox.com with http (RMM6); Tue, 15 Mar 2016 14:29:37 GMT From: "Jeffrey Bouquet" Reply-To: jbtakk@iherebuywisely.com To: "José Pérez" CC: "Matthew Seaman" , "freebsd-current" , "owner-freebsd-current" Subject: Re: [CFT] packaging the base system with pkg(8) Date: Tue, 15 Mar 2016 07:29:37 -0700 (PDT) X-Mailer: RMM6 In-Reply-To: <3a1d11dde8186d73db1b8b32004bdd30@mail.yourbox.net> Message-Id: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 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: Tue, 15 Mar 2016 15:21:39 -0000 On Tue, 15 Mar 2016 08:53:10 +0100, Jos=C3=A9 P=C3=A9rez wro= te: > El 2016-03-03 11:27, Matthew Seaman escribi=C3=B3: > > On 03/02/16 23:54, Glen Barber wrote: > >> Also note (as repeated below), running 'pkg delete -a' will implicitly > >> remove base system packages after they are installed. > >=20 > > This has the potential for many feet to be shot, given that up to now, > > 'pkg delete -a' would always leave you with a viable system. >=20 > Agreed. >=20 > Suggested workaround (a las *grep): create two pkg binaries with=20 > different names: > - "pkg" does what it does now and works on non-base packages by default.= =20 > Need an extra > arg to work on base system > - "syspkg" (or something) works by default on base system >=20 > We'd need way less crutches. >=20 > Regards, >=20 > --- > Jos=C3=A9 P=C3=A9rez > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Hmm...=20 To reiterate this point.......... (1) As a wish here is for more code within pkg-install so that I do not encount= er a situation such as late last night whereupon I had to spend an extra half hour or so figuri= ng out that hplip installed a large number of unwanted additional qt4 ports alongside the cups upgrade = with pkg, ... so that a parameter or usual output would show NEW PORTS TO BE INSTALLED along= side each one from WHICH port is the request to install the new dependency... as a backdrop for this that I just thought of (2)... .... what if pkg on the base system deletes SOONER THAN THE USUAL make-del= ete-old that PREVENTS/HALTS the successful completion of the pkg updating base? So= mething critical to pkg itself proceeding? As a typo or bug?...... Maybe anothe= r cluster of testing=20 machines and weeks of testing before each pkg-release-avail or pkg-stable-a= vail became=20 known to FreeBSD users in emails... and that would maybe preclude pkg OF BA= SE from being useful for CURRENT installs due to a lack of testing, and/or make cur= rent upgrades more risky. Unless of course pkg of base is NOT relevant to CURRENT builds. In= which case please pardon the additional text slipping into this two-part food for thou= ght... little time to keep current on FreeBSD details vs FreeBSD ordinary usage cases.=