From owner-freebsd-ports@FreeBSD.ORG Thu Oct 14 03:13:51 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 AA77316A4CE; Thu, 14 Oct 2004 03:13:51 +0000 (GMT) Received: from toxic.magnesium.net (toxic.magnesium.net [207.154.84.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E2A243D1F; Thu, 14 Oct 2004 03:13:51 +0000 (GMT) (envelope-from adamw@magnesium.net) Received: by toxic.magnesium.net (Postfix, from userid 1252) id D8302DA874; Wed, 13 Oct 2004 20:13:50 -0700 (PDT) Date: Wed, 13 Oct 2004 23:13:50 -0400 From: Adam Weinberger To: David O'Brien Message-ID: <20041014031350.GS22274@toxic.magnesium.net> References: <416C0DE8.3000004@struchtrup.com> <416C35A5.4040703@vonostingroup.com> <20041013123840.GB1301@FreeBSD.org> <20041013193432.GA53895@hub.freebsd.org> <416DAB52.5070404@struchtrup.com> <20041014024646.GB90017@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041014024646.GB90017@dragon.nuxi.com> X-Editor: Vim 6.2 http://www.vim.org X-Mailer: Mutt 1.5 http://www.mutt.org X-URL: http://www.vectors.cx X-ASL: 6/m/behind you User-Agent: Mutt/1.5.4i cc: Eivind Eklund cc: Frank Laszlo cc: freebsd-ports@FreeBSD.org cc: Sebastian Schulze Struchtrup 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: Thu, 14 Oct 2004 03:13:51 -0000 >> (10.13.2004 @ 2246 PST): David O'Brien said, in 1.8K: << > On Thu, Oct 14, 2004 at 12:25:22AM +0200, Sebastian Schulze Struchtrup wrote: > > 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. > > You only have to be as famiar with pre-built package flavors as you are > with build OPTIONS. How do you know which compile options you want? For > which package flavor to install, you can use 'sysinstall' which will > show you both the 1-line desciption along with the longer one to help you > in your choices. > > > > >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? > > Currently one defines WITH_* knobs and then compiles. One of the WITH_ > knobs is the default GUI build. For non-X11 GUI there is the 'vim-lite' > port. >> end of "Re: alternative options for ports" from David O'Brien << Ohhh... you know, until now, I didn't know that that's what the vim-lite package is. David, could you please consider making note of that in the COMMENT string or by creating a vim-lite/pkg-descr or something? I had thought that the only way to get vim without X11 was to compile vim -DWITHOUT_X11. # Adam -- Adam Weinberger adamw@magnesium.net || adamw@FreeBSD.org adamw@vectors.cx || adamw@gnome.org http://www.vectors.cx