Date: Sun, 13 Feb 2000 23:13:04 -0800 From: Doug Barton <DougB@simplenet.com> To: Alexander Langer <alex@big.endian.de> Cc: "R.I.Pienaar" <rip@pinetec.co.za>, Brett Taylor <brett@peloton.runet.edu>, Matthew Hunt <mph@astro.caltech.edu>, ports@FreeBSD.ORG Subject: Re: linux user meta port Message-ID: <38A7AB00.7FAAD35C@simplenet.com> References: <20000202123022.A2477@wopr.caltech.edu> <Pine.BSF.4.10.10002021706150.11268-100000@peloton.runet.edu> <20000203121339.D1205@pinetec.co.za> <20000203112317.B11391@cichlids.cichlids.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Alexander Langer wrote:
>
> Thus spake R.I.Pienaar (rip@pinetec.co.za):
>
> > question is do I accept defaults for those, or give the user some help when he
> > doesnt specify options?
>
> another idea:
> a make choice target or such, that will call a script to dialog(1).
> There you can choose the options and it'll will compile automatically
> with
> make PORT_MAIL=mutt etc set.
In general I like this idea. However if you're going to make a port that
installs stuff which is common to linux installations, making the user pick
between different programs for a given task defeats your definition of
"common." :) I would put references to these additional options in your
@ECHO file, and have the port stick to installing things that are truly
common.
Good luck,
Doug
--
"Welcome to the desert of the real."
- Laurence Fishburne as Morpheus, "The Matrix"
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?38A7AB00.7FAAD35C>