From owner-freebsd-ports@FreeBSD.ORG Wed Oct 13 22:24:35 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D21316A4F5; Wed, 13 Oct 2004 22:24:35 +0000 (GMT) Received: from mail.struchtrup.de (mail.struchtrup.de [80.190.247.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E86743D5A; Wed, 13 Oct 2004 22:24:32 +0000 (GMT) (envelope-from seb@struchtrup.com) Received: from dialin-145-254-088-136.arcor-ip.net ([145.254.88.136]) by mail.struchtrup.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.42 (FreeBSD)) id 1CHra5-0003Ai-UW; Wed, 13 Oct 2004 22:26:50 +0000 Message-ID: <416DAB52.5070404@struchtrup.com> Date: Thu, 14 Oct 2004 00:25:22 +0200 From: Sebastian Schulze Struchtrup User-Agent: Mozilla Thunderbird 0.6 (X11/20040517) X-Accept-Language: en-us, en MIME-Version: 1.0 To: obrien@freebsd.org References: <416C0DE8.3000004@struchtrup.com> <416C35A5.4040703@vonostingroup.com> <20041013123840.GB1301@FreeBSD.org> <20041013193432.GA53895@hub.freebsd.org> In-Reply-To: <20041013193432.GA53895@hub.freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Struchtrup-MailScanner-Information: Please contact the ISP for more information X-Struchtrup-MailScanner: Found to be clean X-MailScanner-From: seb@struchtrup.com cc: Frank Laszlo cc: Eivind Eklund cc: freebsd-ports@FreeBSD.org Subject: Re: alternative options for ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Oct 2004 22:24:35 -0000 David O'Brien wrote: >OPTIONS isn't the answer -- they don't do anything for 'pkg_add -r' >users. > That's a problem. I agree. But what about ports having 10 different options? Probably it would make sense to build the most common configurations in such a case. On the other hand, the user must know which package to add for a given port with a given config. I am not familiar with packages and package building in detail. >Since we go to a *lot* of work building packages and making them >available there must be a huge number of consumers of them. We should be >making more port variations. vim-gtk, vim-kde, vim-athena, vim-motif for >instance. That way a pkg_add user and get what they want. > > I assume that this is currently done by hand? To say build the vim port with options --with-gtk, --with-kde and --with_arena? Or is there a way to set this in a Makefile? Not only altering the package name from vim to vim-xxx, but to define configurations for automatic package building?