From owner-freebsd-pkg@FreeBSD.ORG Mon Feb 23 17:46:28 2015 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 55017D9E; Mon, 23 Feb 2015 17:46:28 +0000 (UTC) Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D5A64608; Mon, 23 Feb 2015 17:46:27 +0000 (UTC) Received: by wggz12 with SMTP id z12so266142wgg.2; Mon, 23 Feb 2015 09:46:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=u9umvsVKdwb/iYJAU9eWA01rKV2Wum0rZxfZZIxc4c0=; b=QASQsSVEG+2lh/tSo9rSzsF2KqjIPxQVkdOmmms6/OJ+S33M7HbbaDwM/ak/v0wi0t 1OQjgJ0PNV9XpXFpGL1w1auIspzW986z+4MyLBaTIxY2ngAjmc0p/BcYAYyL9OxXVyNN jy+WX24D1f1lll1PqY6uAKfrjCBJGAt6TvZXJ3ERIsxP9RX28miOisyhgYwEmQla/zdO 1Rcz+e0+foaKrW4IlOsqiLSS7OA/yncUmF/ES2Qedpqa4lSVLEQNh+qMzBXNPLn5GL8m AId8Bnc25gfA3gR4JdY1RrA7zbbuEJcmLlz48ilJBprEsv7iPjo/u0Y8unOIaDUKP4qG KSeQ== X-Received: by 10.194.201.103 with SMTP id jz7mr25330396wjc.14.1424713586157; Mon, 23 Feb 2015 09:46:26 -0800 (PST) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id dj4sm56545301wjc.13.2015.02.23.09.46.24 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 23 Feb 2015 09:46:25 -0800 (PST) Sender: Baptiste Daroussin Date: Mon, 23 Feb 2015 18:46:22 +0100 From: Baptiste Daroussin To: Ivan Voras Subject: Re: Upgrading php with pkg Message-ID: <20150223174622.GD34473@ivaldir.etoilebsd.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mJm6k4Vb/yFcL9ZU" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-pkg@freebsd.org 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:46:28 -0000 --mJm6k4Vb/yFcL9ZU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 23, 2015 at 05:48:46PM +0100, Ivan Voras wrote: > Hi, >=20 > It's time for my yearly rant about pkg seemingly not being able to upgrade > whole sets of dependencies while installing or upgrading packages. >=20 > In short, if we have this: >=20 > package A depends on package B, which depends on package C >=20 > ...upgrading package B *must always* result in an upgrade to package A, a= nd > *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 new= er > version of package C). >=20 > 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. >=20 > If this is not done, we have the situation described here: > http://ivoras.net/blog/tree/2015/Feb-why-freebsds-pkg-sucks.html >=20 > The post is somewhat strongly worded, and I believe it will be even more > strongly worded a year from now ;) The only problem here is the lack of developers and of time, btw this is not interdependency this is cherry-picking, interdependency works well when upgrading all at one. Beside what some people would like the ports tree and packages is a whole thing. Either you upgrade everything or you do not... This is what non frozen packages gives you, you may like it or not this is = how it is, and it is mostly impossible to prevent that without an important wor= k on both the port side and the pkg side. BTW: using strong words might sound fun, but the only reaction achieved with that is demotivation... We are doing what we can with very few resources, i= f one want to see this fixed and/or properly handled this is clearly not with str= ong words... Bapt --mJm6k4Vb/yFcL9ZU Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlTrZ24ACgkQ8kTtMUmk6EyYxQCeLitStxwOPbFShdB9Zx9l4OkK +7sAoMLX3kt/fMjXXi6HQ0sNlOWHpKzX =rjG0 -----END PGP SIGNATURE----- --mJm6k4Vb/yFcL9ZU--