From owner-freebsd-ports@freebsd.org  Thu Feb  9 17:00:54 2017
Return-Path: <owner-freebsd-ports@freebsd.org>
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 C2F05CD68C6
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Thu,  9 Feb 2017 17:00:54 +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 8833BB71;
 Thu,  9 Feb 2017 17:00:54 +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 10330839B9;
 Thu,  9 Feb 2017 18:00:53 +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 <franco@lastsummer.de>
In-Reply-To: <9155c628-de63-63ba-1cf0-5c33cea82725@FreeBSD.org>
Date: Thu, 9 Feb 2017 18:00:53 +0100
Cc: freebsd-ports@freebsd.org
Content-Transfer-Encoding: 7bit
Message-Id: <E943AB0C-C682-4E5E-8B73-CED267D7A8DB@lastsummer.de>
References: <dvvl9chf9h22dpjto35d44enid819p9rnc@4ax.com>
 <h91m9cpbmp6js1km1bson74he5uuui9r6h@4ax.com>
 <1c6cccac-b151-d13c-c763-b336c4680118@freebsd.org>
 <ndjm9cl4samqgioi25ro8p2q6liimvr1h4@4ax.com>
 <35a953e3-918b-fc32-d990-51f7da16c884@FreeBSD.org>
 <AE0D514C-D235-462D-B31D-66FC619D9F4D@lastsummer.de>
 <20170209161249.GL2092@kib.kiev.ua>
 <73E2F71C-0C7E-49A3-8D98-3AECA8F40F99@lastsummer.de>
 <bdd0628a-6794-97de-b818-d871a685e7a2@FreeBSD.org>
 <3FB972B7-F9B7-4EAE-9C06-9DCECD5F6531@lastsummer.de>
 <9155c628-de63-63ba-1cf0-5c33cea82725@FreeBSD.org>
To: Steve Wills <swills@FreeBSD.org>
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 <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 17:00:54 -0000


> On 9 Feb 2017, at 5:53 PM, Steve Wills <swills@FreeBSD.org> wrote:
> 
> What would enforcement look like? Something like "Sorry, you can't pkg
> update because this system isn't supported any more."? But how would
> that be possible without also breaking things for those who build/ship
> their own OS and packages?

Let me try another way:

Since pkg has feature macros for building correctly on different
FreeBSD versions, namely 10.0, 10.1, 10.2 and 10.3, the way to
provide binaries without missing symbols is to build pkg with a
fixed set of feature macros for 10.0.

I've done this for projects to retain upgrade paths.  It's not
hard.  It doesn't violate a policy or promise FreeBSD makes, does
it?


Cheers,
Franco