Date: Mon, 8 Oct 2012 10:16:58 +0100 From: Chris Rees <utisoft@gmail.com> To: Thomas Mueller <mueller23@insightbb.com> Cc: FreeBSD Mailing List <freebsd-ports@freebsd.org>, "Ronald F. Guilmette" <rfg@tristatelogic.com> Subject: Re: Building Ports: Is there a "make" equivalent for --batch ? Message-ID: <CADLo838E7J=p0HXrW9oYScOPjeA6j5r=nXqb3qDEiccs6ceLqQ@mail.gmail.com> In-Reply-To: <D5.88.07499.AD092705@smtp02.insight.synacor.com> References: <D5.88.07499.AD092705@smtp02.insight.synacor.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8 Oct 2012 09:38, "Thomas Mueller" <mueller23@insightbb.com> wrote:
>
> from Polytropon:
>
> > A workaround (and not directly the answer to your question) is
> > to process the config dialogs before starting the build:
>
> > # make config-recursive
>
> > Once set, the options won't be requested on a second run.
> > According to "man 7 ports", there's a BATCH setting, but
> > it is descibed as:
>
> > If defined, only operate on a port if it can be
> > installed 100% automatically.
>
> This helps ("make config-recursive"), but depending on options chosen and
> resulting added dependencies, the config dialog can appear again. So I
run
> "make config-recursive" repeatedly until it just returns to shell prompt.
> That works most of the time.
>
> My biggest reason for doing this is to be able to run the portmaster or
make
> command with "|& tee build.log" at the end, and config dialog is very
> hostile to this. It is also helpful to be able to allow a long
portmaster or
> portupgrade, or package build, to run unattended.
make BATCH=yes
Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo838E7J=p0HXrW9oYScOPjeA6j5r=nXqb3qDEiccs6ceLqQ>