Re: Using portconf and /usr/local/etc/ports.conf
--- James Long <[EMAIL PROTECTED]> wrote:
> > Date: Mon, 9 Oct 2006 05:15:28 -0700 (PDT)
> > From: backyard <[EMAIL PROTECTED]>
> > Subject: Re: Using portconf and
> /usr/local/etc/ports.conf
> > To: freebsd-questions@freebsd.org
> > Message-ID:
>
<[EMAIL PROTECTED]>
> > Content-Type: text/plain; charset=iso-8859-1
> >
> > if ruby uses ncurses, that blue menu thing, you
> have
> > to add BATCH=Yes as a build option to skip the
> menu
> > and build it with the options you have selected.
>
> You missed the point. If I were to set batch mode
> on, then
I meant set BATCH as an option only to the ruby knob,
then it would only apply to that build.
> it would just build WITHOUT the options I selected.
> The fact
> that the config box came up with RDOC and IPV6 still
> selected
> suggests to me that portconf isn't recognizing my
> entries in
> ports.conf.
maybe but if portconf doesn't automatically apply a
BATCH build then you WILL ALWAYS get a screen that
will default to what is in the Makefile, not what you
passed to make -DFOO -DBAR. Unless you use the
previous options but I'm not certain how to tell make
to use the existing options file.
>
> > don't know much about portconf
>
> Thanks all the same.
>
is portconf supposed to automagically apply a batch
build??? I'm confused...
that is why I keep it simple with stuff like this
.if {CURDIR:M/usr/ports*}
include /foo/bar/ports.conf
.endif
in make.conf
I also do stuff like that to include sup files so I
can independantly update ports and src because when
both are set in the make.conf it seems to always
update both. sometimes this is not what I really want.
and in ports.conf
.if {CURDIR:M*/lang/ruby18}
# comment out all the build options
# from the Makefile copyed in for reference
#
BATCH=YES
WITHOUT_IPV6=yes
WITH_FOOBAR=YES
WITH_STUFF=no # == WITH_STUFF=YES, use WITHOUT_STUFF
.endif
there was a nice thing I found on google when
searching
retaining options portupgrade
or something along those lines. Why use ports to do
something make already understands. At least that is
my logic. especially if you have to type up a
configuration file anyway... You could keep things in
just make.conf but things get messy after a while.
good luck
-brian
>
> Jim
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Using portconf and /usr/local/etc/ports.conf
> Date: Mon, 9 Oct 2006 05:15:28 -0700 (PDT) > From: backyard <[EMAIL PROTECTED]> > Subject: Re: Using portconf and /usr/local/etc/ports.conf > To: freebsd-questions@freebsd.org > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=iso-8859-1 > > if ruby uses ncurses, that blue menu thing, you have > to add BATCH=Yes as a build option to skip the menu > and build it with the options you have selected. You missed the point. If I were to set batch mode on, then it would just build WITHOUT the options I selected. The fact that the config box came up with RDOC and IPV6 still selected suggests to me that portconf isn't recognizing my entries in ports.conf. > don't know much about portconf Thanks all the same. Jim ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Using portconf and /usr/local/etc/ports.conf
--- James Long <[EMAIL PROTECTED]> wrote:
> I am trying to migrate my
> /usr/local/etc/pkgtools.conf into
> /usr/local/etc/ports.conf. I'm not sure I have the
> ports.conf
> syntax correct, or that the entries I'm making are
> being
> recognized.
>
> I've installed the sysutils/portconf port
> successfully, and
> my make.conf is:
>
> monitor : /root# cat /etc/make.conf
> CPUTYPE?=p3
>
> NO_PROFILE= true
> USA_RESIDENT=YES
>
> # 2005-12-19 to build sendmail without IPv6
> NO_INET6=YES
>
> # added by use.perl 2006-01-05 14:23:56
> PERL_VER=5.8.7
> PERL_VERSION=5.8.7
> # Begin portconf settings
> # Do not touch these lines
> .if !empty(.CURDIR:M/usr/ports*) &&
> exists(/usr/local/libexec/portconf)
> _PORTCONF!=/usr/local/libexec/portconf
> .for i in ${_PORTCONF:S/|/ /g}
> ${i:S/%/ /g}
> .endfor
> .endif
> # End portconf settings
>
>
> I have this line in /usr/local/etc/ports.conf for
> ruby18:
>
> lang/ruby18: WITHOUT_RDOC=1 | WITHOUT_IPV6=1
>
if ruby uses ncurses, that blue menu thing, you have
to add BATCH=Yes as a build option to skip the menu
and build it with the options you have selected.
>
>
> I then get the build options dialogue box for ruby
> 1.8.5_1,1 with the
> tick boxes for IPV6 and RDOC checked, even though I
> have ports.conf
> entries to turn them off.
>
> Is this my goof, or is something wrong with
> portconf?
>
don't know much about portconf, I configure my ports
directly with make.conf and a seperate file ports.conf
that gets included in the build when in the ports tree
I am. But whith what you describe the batch option
needs to be set because the build dialog uses it's own
defaults separate from command line flags, and if your
setting command line flags there is no need to use the
dialog box.
-brian
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
