Ok so then in my
/usr/local/etc/pkgtools.conf
MAKE_ARGS
I put for individual ports.
MAKE_ARGS = {
'lang/php4' = '-DBATCH WITHOUT_CGI=1 WITH_APACHE=1 WITH_MAILHEAD=1
WITHOUT_FASTCGI=1 WITHOUT_PATHINFO=1 WITH_OPENSSL=1 WITH_ZLIB=1',
}
Or to affect all ports
MAKE_ARGS = {
'*' = '-DBATCH',
'lang/php4' = 'WITHOUT_CGI=1 WITH_APACHE=1 WITH_MAILHEAD=1
WITHOUT_FASTCGI=1 WITHOUT_PATHINFO=1 WITH_OPENSSL=1 WITH_ZLIB=1',
}
Will the second method work to hide the options on all ports?
Thanks very much. It should work but I'm rebuilding my world right now so I
can't test it.
LOL carpetsmoker. What a name.
Thanks,
Charlie.
-Original Message-
From: Martin Tournoij [mailto:[EMAIL PROTECTED]
Sent: Friday, January 19, 2007 4:13 AM
To: Charlie Hynson III; freebsd-questions@freebsd.org
Subject: Re: Hide ports make options/config
On Fri, 19 Jan 2007 08:21:07 -, Charlie Hynson III
[EMAIL PROTECTED] wrote:
I am making myself an easy install sh shell script that configures my own
basic setup on FreeBSD 6.2 Release. Wondering how I tell make when
installing a port not to ask me make options/config (silent install). For
all ports and or individual ports. Since I have my make options set in
pkgtools config for sysutils/portupgrade.
For example portupgrade -RN /usr/ports/lang/php4
Will ask me make options which I have already set. How do I hide the
options.
I tried searching a few places before asking with no luck.
P.S.
Thanks FreeBSD Team for another great release so far 6.2 Release is
running
really smooth on my P4 2.6 i386 system without any problems. By default
FreeBSD 6.2 Release works with my re0 1000/baseTX Full Duplex LinkSys
Gigabit NIC. Which really impresses me since I have to install a driver
on
windows 2003 server enterprise before the card works. Not FreeBSD!!!
Thanks,
Charlie
-DBATCH
For example:
make install -DBATCH [OTHER SWITCHES]
Hope this helps.
Windows 2003 probably has the driver for your NIC, but can't find because
your card is one revision higher, let's say Gigabit 123b, and windows only
has a driver for Gigabit123a or something like that.
Quite often (~90% of the time) this is the case on Windows 2000 and XP
when it can't find a driver.
One (or a few) revisions higher or lower doesn't matter for the driver.
although I don't have any experience with Windows 2003, I think I can
safely assume this is the case for windows 2003 to.
You will have to select the driver manually.
Martin
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
