From owner-freebsd-ports@freebsd.org Thu Feb 9 17:07:27 2017 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 BE620CD6DE5 for ; Thu, 9 Feb 2017 17:07:27 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from host64.shmhost.net (unknown [IPv6:2a01:4f8:a0:51d6::108:1]) (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 8447913C0; Thu, 9 Feb 2017 17:07:27 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from francos-mbp.homeoffice.local (dslb-092-078-013-237.092.078.pools.vodafone-ip.de [92.78.13.237]) by host64.shmhost.net (Postfix) with ESMTPSA id CF9868241A; Thu, 9 Feb 2017 18:07:25 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?! From: Franco Fichtner In-Reply-To: Date: Thu, 9 Feb 2017 18:07:25 +0100 Cc: freebsd-ports@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: <37CCAB80-C18B-4C29-B196-FEC5ECAF551A@lastsummer.de> References: <1c6cccac-b151-d13c-c763-b336c4680118@freebsd.org> <35a953e3-918b-fc32-d990-51f7da16c884@FreeBSD.org> <20170209161249.GL2092@kib.kiev.ua> <73E2F71C-0C7E-49A3-8D98-3AECA8F40F99@lastsummer.de> <3FB972B7-F9B7-4EAE-9C06-9DCECD5F6531@lastsummer.de> <9155c628-de63-63ba-1cf0-5c33cea82725@FreeBSD.org> To: Steve Wills X-Mailer: Apple Mail (2.3259) X-Virus-Scanned: clamav-milter 0.99.2 at host64.shmhost.net X-Virus-Status: Clean X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Feb 2017 17:07:27 -0000 > On 9 Feb 2017, at 6:03 PM, Steve Wills wrote: > > Just because you don't use any features of the newer version doesn't > mean it's safe to run binaries built for the newer version on the older > version, as far as I understand it. True. :) Yet the reports are for missing symbols in pkg and how to fix. It beats pulling a ports tree and rebuilding pkg which may or may not end up being replaced by a newer repo version on the next pkg upgrade. Plus you still get to garbage-collect compatibility features during major upgrade jumps. Fixing this issue in 25k at the same times ends up delaying a workable solution, whatever it may be. pkg first, then the rest, no? Cheers, Franco