From owner-freebsd-ports@FreeBSD.ORG Wed Oct 13 22:53:19 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 203DA16A4CE; Wed, 13 Oct 2004 22:53:19 +0000 (GMT) Received: from mail.struchtrup.de (mail.struchtrup.de [80.190.247.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id C46D743D5A; Wed, 13 Oct 2004 22:53:18 +0000 (GMT) (envelope-from seb@struchtrup.com) Received: from dialin-145-254-091-059.arcor-ip.net ([145.254.91.59]) by mail.struchtrup.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.42 (FreeBSD)) id 1CHs1y-0003Dy-2D; Wed, 13 Oct 2004 22:55:38 +0000 Message-ID: <416DB213.3020708@struchtrup.com> Date: Thu, 14 Oct 2004 00:54:11 +0200 From: Sebastian Schulze Struchtrup User-Agent: Mozilla Thunderbird 0.6 (X11/20040517) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Frank J. Laszlo" References: <416C0DE8.3000004@struchtrup.com> <416C35A5.4040703@vonostingroup.com> <20041013123840.GB1301@FreeBSD.org> <20041013193432.GA53895@hub.freebsd.org> <416DAB52.5070404@struchtrup.com> <416DAD75.7000504@vonostingroup.com> In-Reply-To: <416DAD75.7000504@vonostingroup.com> Content-Type: text/plain; charset=ISO-8859-1; 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: 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:53:19 -0000 Frank J. Laszlo wrote: >>> 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? > > > using vim as an example, currently the port recognises env variables > like most other ports do. e.g. WITH_GTK2, WITH_ATHENA etc.. these > generally make changes to the CONFIGURE_ARGS. Of course, that's what I've meant with --with_(gtk2|athena|kde). I should go to bed now. > Regarding package building, there is an option (with the vim port) > for PACKAGE_BUILDING which builds with the most common options. I'm > not exactly sure what kind of answer you were looking for, but just my > little input on the subject :) I thought of a way to specify configurations to build several packages of the same port (of course with a diff. suffix) [called port variations by David] E.g. build the vim port three times, First, with default options and WITH_GTK2 resulting in a package vim-gtk2 Then with default options and WITH_KDE resulting in vim-kde And then with default options and WITH_ATHENA resulting in vim-athena. I don't know if there is a clean solution, but I remember that this is (at least in some cases) handled with diff ports and setting MASTERDIR and including the master's makefile. But this would lead to many add. ports just for package building...