From owner-freebsd-pkg@FreeBSD.ORG Mon Feb 23 17:47:26 2015 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8751DDF0 for ; Mon, 23 Feb 2015 17:47:26 +0000 (UTC) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 57DDF622 for ; Mon, 23 Feb 2015 17:47:25 +0000 (UTC) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id D627D20A76 for ; Mon, 23 Feb 2015 12:47:23 -0500 (EST) Received: from web3 ([10.202.2.213]) by compute4.internal (MEProxy); Mon, 23 Feb 2015 12:47:24 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:x-sasl-enc:from:to :mime-version:content-transfer-encoding:content-type:subject :date:in-reply-to:references; s=smtpout; bh=XaLbibJZqFhCWA3XbrYO rCJ9YCg=; b=h10Jnx2zjzr8UWUV+hhcvt1f0HdusylbRtpiJ6724sEAte/XykKd nML0ixkNEj/Z1p+l8LcXzC/9tNyPu7DndVKVXq2XpY3jho9JT4OUik70tDN4woNF Z1SMPaExPr6qV/w7w7KuBhSPXX74ZTSBr8BgI8Urm+BB30N5IXMx+F4= Received: by web3.nyi.internal (Postfix, from userid 99) id 6EEBE10E5B5; Mon, 23 Feb 2015 12:47:24 -0500 (EST) Message-Id: <1424713644.2437211.231310185.721AACDF@webmail.messagingengine.com> X-Sasl-Enc: gKSeLqKkrQRufGIwbC41qivZss7ebj/l/7Ss5oYLls1A 1424713644 From: Mark Felder To: freebsd-pkg@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-4ba7306c Subject: Re: Upgrading php with pkg Date: Mon, 23 Feb 2015 11:47:24 -0600 In-Reply-To: References: X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2015 17:47:26 -0000 On Mon, Feb 23, 2015, at 10:48, Ivan Voras wrote: > Hi, > > It's time for my yearly rant about pkg seemingly not being able to > upgrade > whole sets of dependencies while installing or upgrading packages. > > In short, if we have this: > > package A depends on package B, which depends on package C > > ...upgrading package B *must always* result in an upgrade to package A, > and > *must* cause an upgrade of package C *iff* the new version of package B > is > linked with a different version of package C (e.g. if it depends on a > newer > version of package C). > > Using heuristics such as checking versions encoded in .so filenames are > rarely enough because (upstream) developers are lazy. I can give examples > from the PHP-Apache-PostgreSQL stack at request. > > If this is not done, we have the situation described here: > http://ivoras.net/blog/tree/2015/Feb-why-freebsds-pkg-sucks.html > > The post is somewhat strongly worded, and I believe it will be even more > strongly worded a year from now ;) > While I do agree that # pkg install php53-fileinfo should list more packages that need to be upgraded, you're walking on thin ice by installing new packages related to existing ones without upgrading all of your packages first. The following is absolutely unsupported last I checked: # pkg upgrade php53 Upgrade all of your packages or none. The stability of the packages are very much reliant on all packages being from the exact same package set / SVN revision. Mixing packages when packages/ports is a rolling release has always been a dangerous game to play. If you require a stable set of package like that you should be using the quarterly package sets. In that situation you wouldn't have received php53-fileinfo-5.3.29; it would have been the exact same as the existing packages from that quarterly set.