From owner-freebsd-ports@freebsd.org Wed Sep 30 23:17:13 2015 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 46837A0B498 for ; Wed, 30 Sep 2015 23:17:13 +0000 (UTC) (envelope-from freebsd-ports-local@be-well.ilk.org) Received: from be-well.ilk.org (be-well.ilk.org [23.30.133.173]) by mx1.freebsd.org (Postfix) with ESMTP id 1ED5E1D96 for ; Wed, 30 Sep 2015 23:17:13 +0000 (UTC) (envelope-from freebsd-ports-local@be-well.ilk.org) Received: from lowell-desk.lan (router.lan [172.30.250.2]) by be-well.ilk.org (Postfix) with ESMTP id 08D5D33C24; Wed, 30 Sep 2015 19:17:06 -0400 (EDT) Received: by lowell-desk.lan (Postfix, from userid 1147) id 60A1C39819; Wed, 30 Sep 2015 19:16:59 -0400 (EDT) From: Lowell Gilbert To: freebsd-ports@freebsd.org Subject: Re: Ports requires pkg 1.6.0, but 1.5.6 is the latest available References: <5609D023.70402@bluerosetech.com> <560A47FE.6010507@bluerosetech.com> <560AAD43.5000207@unfs.us> <560AF5CF.2080909@bluerosetech.com> <20150929213632.GA23442@ivaldir.etoilebsd.net> <44bncjsn5d.fsf@be-well.ilk.org> <44eghffsoq.fsf@totally-fudged-out-message-id> Date: Wed, 30 Sep 2015 19:16:59 -0400 In-Reply-To: <44eghffsoq.fsf@totally-fudged-out-message-id> (Roger Marquis's message of "Wed, 30 Sep 2015 15:11:52 -0700") Message-ID: <448u7nfqfo.fsf@lowell-desk.lan> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Sep 2015 23:17:13 -0000 "Roger Marquis" writes: > For the vast majority of ports and packages it won't make any difference > whether they are installed are from head, quarterly and/or archives (in my > experience, options dependencies aside). Isn't the issue here a dependency on > the version of 'pkg' being enforced by 'pkg'? If so shouldn't this be fixed > in 'pkg'? Sort of. The issue is that trying to build some ports on head requires the version of pkg that's in head; the version that's on the quarterly branch won't do. pkg(8) is more sensitive to this than other ports, because it is used for installing into the production filesystem, but it could happen with many ports. The scenario is that a port on head depends on a recent version of another port, and that other port is still on an older version on the quarterly branch. Most ports will work, most of the time, but if you install some things from head and others from quarterly, there *will* be cases occasionally where the dependencies of a port on head cannot be met by the ports on quarterly. As far as I can see, if someone wants to use the quarterly branch with pkg, they will have fewer problems if they use the quarterly branch for building from source as well. That means checking out the quarterly branch from Subversion, which the Handbook doesn't currently explain how to do. [The portsnap ecosystem, as far I've been able to determine, does not support branches.] In short, there is nothing broken in pkg(8) per se. I am pretty sure this problem does not come up if you do everything from quarterly or everything from head; it's strictly an issue of conflicts between the two. Furthermore, I suspect that if the original poster had updated his quarterly-branch version of pkg to the head version, he probably would have been able to build the other port from the head tree. There are a few places where I may have gone wildly off the track. The most likely one is that real conflicts between quarterly and head may be vastly less likely than my estimate; in that case, the measures described by bapt@ would be the optimum achievable strategy.