From owner-freebsd-ports@FreeBSD.ORG Fri May 8 13:17:47 2009 Return-Path: Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C0B61065673 for ; Fri, 8 May 2009 13:17:47 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 4B6098FC12 for ; Fri, 8 May 2009 13:17:45 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA19883; Fri, 08 May 2009 16:17:43 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4A0430F6.4080202@icyb.net.ua> Date: Fri, 08 May 2009 16:17:42 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.21 (X11/20090406) MIME-Version: 1.0 To: Ashish SHUKLA References: <4A01C995.1080808@icyb.net.ua> <86hbzwvzsd.fsf@chateau.d.lf> <4A03F50B.6050908@icyb.net.ua> <86tz3v6d44.fsf@chateau.d.lf> In-Reply-To: <86tz3v6d44.fsf@chateau.d.lf> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=KOI8-U Content-Transfer-Encoding: 7bit Cc: freebsd-ports@FreeBSD.ORG Subject: Re: split xcbgen from xcb-proto X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 May 2009 13:17:47 -0000 on 08/05/2009 14:35 Ashish SHUKLA said the following: > Well no ideas about netbsd's pkgsrc system, but debian is a package > based system. Being a package based system, you've to create a separate > package for each combination of options you're going to support. IMHO, > FreeBSD is not a package based system primarily. Well, let's not make decisions for other people. It's great to have a combined ports/packages system and it's nice to always treat it as such. > It is ports based and > in ports based system you've the freedom to specify the OPTIONS with > which you want port to be installed and a package to be built for it. Freedom always comes with burden of choice. I don't see why in this case there should be any choice or why that choice should be on a user. Select PYTHON and a user might have a bloat that he actually doesn't; don't select PYTHON, then later install some port that depends on xcbgen and a user has to deal with a cryptic failure when the new port sees that xcb-proto is installed, but doesn't see xcbgen. Having two ports, one for xcb-proto C core and the other for xcbgen doesn't but any burden on a user and automatically correctly handles dependencies. But this approach is more laborious, of course. > And BtW, WITH_PYTHON is not defined by default which means the default > port will not be built with python support, unless you specifically > requests for it. If this seems okay to you, I can add OPTIONS. -- Andriy Gapon