Date: Thu, 9 Nov 2000 20:29:18 -0600 From: Steve Price <sprice@hiwaay.net> To: Satoshi - Ports Wraith - Asami <asami@FreeBSD.ORG> Cc: Jordan Hubbard <jkh@winston.osd.bsdi.com>, Jimmy <olgeni@uli.it>, ports@FreeBSD.ORG, pine@freebsd.ady.ro, kris@FreeBSD.ORG Subject: Re: 4.2 BETA ISO image Message-ID: <20001109202918.S62344@bonsai.knology.net> In-Reply-To: <vqcpuk4eg44.fsf@silvia.hip.berkeley.edu>; from asami@FreeBSD.ORG on Thu, Nov 09, 2000 at 06:05:31PM -0800 References: <olgeni@uli.it> <21255.973810192@winston.osd.bsdi.com> <vqcpuk4eg44.fsf@silvia.hip.berkeley.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 09, 2000 at 06:05:31PM -0800, Satoshi - Ports Wraith - Asami wrote:
# * From: Jordan Hubbard <jkh@winston.osd.bsdi.com>
#
# * Argh. People keep making ports interactive for "security" reasons
# * but then forget that interactive packages are not handled by sysinstall
# * and should be marked IS_INTERACTIVE so that I can keep them off the CD.
# *
# * I'll remove the pine port from the final CD image, but this goes for any
# * other ports which do the same thing. :-(
#
# Ports marked IS_INTERACTIVE won't be packaged at all for obvious
# reasons -- I won't be able to hit return for packages built from
# cron. :)
Actually I believe he is talking about ports that are interactive on
install (not build). Most (if not all) of these have been fixed to
not require interaction during package builds (nay installs) ...
# Perhaps sysinstall should be fixed? If that is not possible, we can
# introduce a new fixed comment that you can grep for or something.
... which is why I suggested to Jordan (in a private mail apparently
because I haven't seen it come through) that a *very* hackish solution
of handling ports like pine4 would be to add the following lines to
the appropriate spot in sysinstall.
setenv("PACKAGE_BUILDING", "t", 1);
setenv("BATCH", "t", 1);
-steve
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?20001109202918.S62344>