From owner-freebsd-pkgbase@freebsd.org Tue Apr 19 14:39:27 2016 Return-Path: Delivered-To: freebsd-pkgbase@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 1AA2DB1429E; Tue, 19 Apr 2016 14:39:27 +0000 (UTC) (envelope-from dan_partelly@rdsor.ro) Received: from mail.rdsor.ro (mail.rdsor.ro [193.231.238.10]) by mx1.freebsd.org (Postfix) with ESMTP id 5276D1CE1; Tue, 19 Apr 2016 14:39:26 +0000 (UTC) (envelope-from dan_partelly@rdsor.ro) Received: from email.rdsor.ro (ftp.rdsor.ro [193.231.238.4]) by mail.rdsor.ro (Postfix) with ESMTP id 0EE71232E5; Tue, 19 Apr 2016 17:39:25 +0300 (EEST) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Date: Tue, 19 Apr 2016 17:39:37 +0300 From: dan_partelly To: Alfred Perlstein Cc: Julian Elischer , , Glen Barber , Nathan Whitehorn , Sean Fagan , , Subject: Re: [CFT] packaging the base system with pkg(8) In-Reply-To: <57164068.8080800@freebsd.org> References: <20160302235429.GD75641@FreeBSD.org> <57152CE5.5050500@FreeBSD.org> <9D4B9C8B-41D7-42BC-B436-D23EFFF60261@ixsystems.com> <20160418191425.GW1554@FreeBSD.org> <571533B8.6090109@freebsd.org> <20160418194010.GX1554@FreeBSD.org> <57153E80.4080800@FreeBSD.org> <571551AB.4070203@freebsd.org> <5715E1E9.8060507@freebsd.org> <57164068.8080800@freebsd.org> Message-ID: <78fb431d2d9b568fd488fae51a1b5f23@rdsor.ro> X-Sender: dan_partelly@rdsor.ro User-Agent: RoundCube Webmail/0.4-beta X-BeenThere: freebsd-pkgbase@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Packaging the FreeBSD base system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 14:39:27 -0000 > > What should not happen is that this incremental step forward be blocked > by those unwilling to hash out the next steps. > > -Alfred > > While incremental steps forward are great, how do you avoid situations like VNET, where a "good enough" enough implementation, usable in some scenarios lingered for years in kernel, but to this day it suffers from leaks and bugs. Once you go down the path of enabling it in this state, chances are that it will stay that way for more than half a decade.