From owner-svn-src-head@FreeBSD.ORG Fri Nov 30 22:40:52 2012 Return-Path: Delivered-To: svn-src-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4CCE348F; Fri, 30 Nov 2012 22:40:52 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from mx0.deglitch.com (backbone.deglitch.com [78.110.53.255]) by mx1.freebsd.org (Postfix) with ESMTP id 565C08FC12; Fri, 30 Nov 2012 22:40:51 +0000 (UTC) Received: from freebsd (unknown [72.5.114.2]) by mx0.deglitch.com (Postfix) with ESMTPA id 9C47B8FC2B; Sat, 1 Dec 2012 02:40:42 +0400 (MSK) Date: Fri, 30 Nov 2012 14:40:40 -0800 From: Stanislav Sedov To: Baptiste Daroussin Subject: Re: svn commit: r243554 - in head/usr.sbin/pkg_install: add create delete info lib updating version Message-Id: <20121130144040.99559ed924a48b909cbd3c4b@FreeBSD.org> In-Reply-To: <20121129073846.GG97474@ithaqua.etoilebsd.net> References: <201211260511.qAQ5B7DQ002346@svn.freebsd.org> <20121128170032.730be5fab68dba2a09aaa14e@FreeBSD.org> <20121128183422.714562856f27371c95d2a84e@FreeBSD.org> <20121129073846.GG97474@ithaqua.etoilebsd.net> Organization: The FreeBSD Project X-Mailer: carrier-pigeon Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, Eitan Adler X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Nov 2012 22:40:52 -0000 On Thu, 29 Nov 2012 08:38:47 +0100 Baptiste Daroussin mentioned: > > pkg is no more experimental at all, it is not perfect there are large rooms for > improvements, but it is perfectly ready to be used, if you have any concern > about some missing "feature" just report it; > > Concerning a landmine, when you have big flashy lights all over the place: > http://lists.freebsd.org/pipermail/freebsd-ports-announce/2012-October/000032.html > http://lists.freebsd.org/pipermail/freebsd-current/2012-October/037001.html > a fanfare playing in front of it saying beware landsmine: > http://svnweb.freebsd.org/ports?view=revision&revision=305637 > and maps available all over the places to explains where the mine are how to > workaround them, or be mine proof: > http://svnweb.freebsd.org/ports/head/CHANGES (entry 20121010) > http://svnweb.freebsd.org/ports/head/UPDATING (entry 20121010) > > I'd say in that case it is no more considered as a landmine but just a new safe > way. It is a new way forced on users. I didn't ask to use pkgng on my system, neither I got any warning when it silently stopped creating entries in /var/db/pkg. Do you expect all users to read UPDATING and/or svn commit logs each time they update? Switching to pkgng was not a community descision, it was a decision made by a small group of people (alledgedly, considering input from the community). Personally, I don't see why it should be that way, and why the default had to be forceably changed. It is an open question (at least for me) whether pkgng is any better than the old tools, and there is at least on drawback in using pkgng, namely sqlite database, which will make you lose all packages in the case of a small fs corruption. That problem was raised before numerous times starting when developing a new pkg tool was proposed. But it is a design decision, and I respect it. What I don't like is that the switch to the new pkg system lacks any legitemacy, as it was largely a portmgr descision. If instead you ran it alongside for some time and it ended up being used by majority of users compared to the legacy pkg, and then pulled the switch, then it'd a different story. The bottom line is that I ended up with a corrupted pkg database for no particular reason. And it didn't have to be that way. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments