From owner-freebsd-stable@FreeBSD.ORG Mon Nov 4 23:03:09 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D4B31ABF for ; Mon, 4 Nov 2013 23:03:09 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from mail.ultra-secure.de (mail.ultra-secure.de [78.47.114.122]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 33FAD29E9 for ; Mon, 4 Nov 2013 23:03:08 +0000 (UTC) Received: (qmail 15500 invoked by uid 89); 4 Nov 2013 23:01:21 -0000 Received: from unknown (HELO ?192.168.1.201?) (rainer@ultra-secure.de@217.71.83.52) by mail.ultra-secure.de with ESMTPA; 4 Nov 2013 23:01:21 -0000 Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\)) Subject: Re: pkgng: how to upgrade a single port? From: Rainer Duffner In-Reply-To: Date: Tue, 5 Nov 2013 00:01:06 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: 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) 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: Mon, 04 Nov 2013 23:03:09 -0000 Am 04.11.2013 um 23:15 schrieb Adrian Chadd : > 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. >=20 > 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.) >=20 Weren=92t there plans to run a =84stable=93 ports-tree at some point? Does anybody know how large a ports-tree is without GUI-apps? Our internal repo is now just shy of 1000 packages (most php53-modules, = 100+ PERL-modules, some python, ruby, apache, nginx, some java). It=92s a huge effort to stabilize that tree between releases - I can=92t = imagine anybody doing it for the full ports-tree without a couple of = FTEs.