From owner-freebsd-chat@FreeBSD.ORG Tue Dec 4 15:57:19 2012 Return-Path: Delivered-To: freebsd-chat@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4C7A8F80 for ; Tue, 4 Dec 2012 15:57:19 +0000 (UTC) (envelope-from netbsd@marino.st) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) by mx1.freebsd.org (Postfix) with ESMTP id 060D98FC12 for ; Tue, 4 Dec 2012 15:57:18 +0000 (UTC) Received: from [10.31.9.103] (unknown [213.225.137.129]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id A5668435C7; Tue, 4 Dec 2012 09:57:17 -0600 (CST) Message-ID: <50BE1D5B.6060606@marino.st> Date: Tue, 04 Dec 2012 16:57:15 +0100 From: John Marino User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0) Gecko/20120129 Thunderbird/10.0 MIME-Version: 1.0 To: Martin Subject: Re: Fwd: Unified BSD? References: <1352882728.28075.140661153435965.302F0E4C@webmail.messagingengine.com> <87a9tw5qju.fsf@inbox.ru> <87wqwyuyxb.fsf@inbox.ru> <50BDAE0C.90303@marino.st> <50BE1391.7050009@marino.st> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: users@dragonflybsd.org, netbsd-users@netbsd.org, Aleksej Saushev , freebsd-chat@freebsd.org X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Dec 2012 15:57:19 -0000 On 12/4/2012 16:42, Martin wrote: > Don't get me wrong, i am not criticising pkgsrc or intentionally trying > get people offside. > > So aside from the obvious differences and limitations (i.e. manpower, > design of each BSD system) What is stopping per say DragonflyBSD or any > other BSD from using packages from FreeBSD or vice versa through pkgsrc? > > Or is it simply that some choose not to provide back to pkgsrc? > Recent work by myself has proven that it is feasible for DragonFly to use FreeBSD ports collection with an specialized overlay. So there's nothing technically stopping that from happening. Pkgsrc has a goal to be universal, so theoretically all platforms will benefit from contributing because the committer is ideally conscious that multiple platforms use it while FreeBSD ports committers only concern themselves with making the port work on FreeBSD. While pkgsrc supports FreeBSD and OpenBSD, in practice it seems most users of those systems tend to stick with FreeBSD Ports Collection and OpenBSD package system. You can speculate why that is. It takes a ton of work to keep a platform current on pkgsrc (which is why I used the words "theoretically" and "ideally") so somebody from those systems has to do that work, which means they have to consider that work worthwhile. I don't see activity to that effect. Pkgsrc would be happy to have parties from FreeBSD and OpenBSD improve the quality of the packages in the repository, I am quite sure of that. Somebody just needs to donate that energy. John