From owner-freebsd-stable@FreeBSD.ORG Tue Nov 5 01:03:23 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 44671F8A; Tue, 5 Nov 2013 01:03:23 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EB4DC2074; Tue, 5 Nov 2013 01:03:22 +0000 (UTC) Received: from mr2.cc.vt.edu (mr2.cc.vt.edu [198.82.163.74]) by lennier.cc.vt.edu (8.13.8/8.13.8) with ESMTP id rA512p0h028561; Mon, 4 Nov 2013 20:02:51 -0500 Received: from auth1.smtp.vt.edu (auth1.smtp.vt.edu [198.82.161.152]) by mr2.cc.vt.edu (8.14.4/8.14.4) with ESMTP id rA512p5X011384; Mon, 4 Nov 2013 20:02:51 -0500 Received: from gromit.chumby.lan (c-98-249-9-133.hsd1.va.comcast.net [98.249.9.133]) (authenticated bits=0) by auth1.smtp.vt.edu (8.14.4/8.14.4) with ESMTP id rA512mw1024508 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 4 Nov 2013 20:02:49 -0500 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\)) Subject: Re: pkgng: how to upgrade a single port? From: Paul Mather In-Reply-To: Date: Mon, 4 Nov 2013 20:02:48 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <81B1C865-2FE9-40B1-92DE-25A0869854E3@gromit.dlib.vt.edu> References: <527406D2.7010200@intertainservices.com> <1383336649.16326.41750369.298F8E9D@webmail.messagingengine.com> <1383337118.18823.41752849.2502EBFD@webmail.messagingengine.com> <5277E53A.4090208@intertainservices.com> <3884C60E-FFEC-413C-901E-631E2862984B@gromit.dlib.vt.edu> <0AD00FF2-8F68-432D-BC7F-9672AD173163@gromit.dlib.vt.edu> To: Adrian Chadd X-Mailer: Apple Mail (2.1816) X-Spam-Status: No, score=-0.0 required=5.0 tests=RP_MATCHES_RCVD autolearn=disabled version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mr2.cc.vt.edu Cc: FreeBSD Stable , Mike Jakubik X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Nov 2013 01:03:23 -0000 On Nov 4, 2013, at 5:15 PM, Adrian Chadd wrote: > Hi, >=20 > Yes, all the things you've said are correct. >=20 > But once that's all said and done, you're still going to end up > occasionally (or not so occasionally) hitting issues where upgrading a > package without upgrading the dependencies ends up _breaking_ things. I am not disagreeing with any of that, nor am I advocating updating = dependent packages without updating dependencies that are also required = to be updated. (As I said, it is the job of the solver to determine = what must be updated.) But, there are also times when you have disjoint = sets of packages where you would like to update one without updating the = other. It would be nice if there was an obvious way to do that. = (There's a way to do it, but the command name is somewhat unintuitive.) > A lot of what makes yum/apt/etc work is because they have a stable > package set and this hides all of the crap surrounding dependency > changing hell. Things are much more exciting if you run debian-testing > though (ie, you get exactly what you described with openjdk / > apache-solr.) Things can get exciting running ports at times. :-) But, if there's one = thing I rely on pkg to do for me it is to keep track of that = dependency-changing hell. If it tells me I need to update a dependency = and I ignore it, I expect bad things to happen. That is regardless of = how stable or volatile the package set is. I have always admired the NetBSD pkgsrc Quarterly releases, which is = close to getting a -STABLE package set on *BSD. Has there ever been = discussion of a slower-moving Ports set for FreeBSD that only gets = security updates? That would be a nice middle ground between the = glacial progress of RHEL Yum packages and the -CURRENT like Ports as it = is right now. Cheers, Paul.