Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 28 May 2001 15:03:35 +0300
From:      Peter Pentchev <roam@orbitel.bg>
To:        Espen Skoglund <esk@ira.uka.de>
Cc:        Willem van Engen <wvengen@stack.nl>, freebsd-ports@FreeBSD.ORG
Subject:   Re: User-selectable fetch/build/install
Message-ID:  <20010528150335.G588@ringworld.oblivion.bg>
In-Reply-To: <15122.14970.856827.714292@i30nb2.ira.uka.de>; from esk@ira.uka.de on Mon, May 28, 2001 at 01:46:02PM %2B0200
References:  <3B1233D3.6E00AA2A@stack.nl> <15122.14970.856827.714292@i30nb2.ira.uka.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 28, 2001 at 01:46:02PM +0200, Espen Skoglund wrote:
> [Willem van Engen]
> > I'm making a port of the sword project (www.crosswire.org). It's a
> > framework for bible-programs and consists of a library and many
> > modules.  I would like the user to select the desired modules, and
> > then only the selected modules will be downloaded and installed.
> > Other ports (e.g. xmms) made several ports for extra modules
> > (xmms-crossfade, xmms-liveice, ...). But since sword has many
> > modules (>90), I wouldn't consider it practical.  How should I
> > implement this? I could make a subdir containing other ports for all
> > the modules, or make a shellscript doing all this and create a port
> > for that, or create a complex Makefile in the port, ...  Except for
> > the first idea, the pkg-plist would be a problem; it would change
> > when the user selects something else.  Could anyone shine some light
> > on this?
> 
> I can see two obvious solutions here:
> 
>   1. Make bundles of the modules and create packages for these bundles
>      (e.g., ports/editors/xemacs-prog-packages).
> 
>   2. Use a shell script for having the user selecting modules.  The
>      script generates a temporary plist which is used during the
>      install process (e.g., ports/textproc/ispell, sans the shell
>      script).
> 
> Please note that if the latter solution is used you should probably
> also provide a set of ``standard'' modules to be included for
> non-interactive builds.

Another example for build-time configuration can be seen in www/mod_php4:
look at the Makefile and the scripts/configure script.

G'luck,
Peter

-- 
Do you think anybody has ever had *precisely this thought* before?

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010528150335.G588>