portsdb -Uu error

Danny MacMillan flowers at users.sourceforge.net
Sat Sep 10 16:38:55 PDT 2005


martin hudec wrote:
> Hello,
> 
> On Sat, Sep 10, 2005 at 03:27:09PM -0400 or thereabouts, Glenn Sieb wrote:
> > # Make options for various ports
> > WITH_APACHE2=yes
> >
> > .undef PERL_VER
> > .undef PERL_VERSION
> > .undef PERL_ARCH
> > .undef NOPERL
> > .undef NO_PERL
> >
> > # For Courier Authlib
> > WITH_AUTH_MYSQL=1
> > WITH_AUTH_USERDB=1
> > WITH_AUTHDAEMON=1
> >
> > # For ges' wordpress
> > WORDPRESS=wordpress
> > # added by use.perl 2005-06-29 21:11:27
> > PERL_VER=5.8.7
> > PERL_VERSION=5.8.7
> > NOPERL=yes
> >
> > # For ImageMagick
> > WITH_JPEG=yes
> > WITH_TIFF=yes
> > WITH_PNG=yes
> >
> > # SpamAssassin Arguments
> > WITH_SPF_QUERY=1
> > WITH_MYSQL=1
> > WITH_TOOLS=1
> > USE_SQLDB=1
> 
>   Just offtopic reply:
> 
>   It might be better actually for you to define various compilation
>   options for ports not in /etc/make.conf but define them while building
>   that port and later (I assume this is the reason why you have options
>   in make.conf) during portupgrade you can take them (set them) from
>   (to) /usr/local/etc/pkgtools.conf. Look for MAKE_ARGS.. these are
>   arguments and options used during portupgrade.

I have a contradictory opinion.  I think defining the options in
/etc/make.conf is ideal, since it is the only place that the options are
guaranteed to be used no matter how you decide to build ports.  Whether
you use portupgrade, portmanager, or just cd into the port directory and
make install, options defined in make.conf will be used.  If you do have
options that apply only to particular ports you can partition them using
the method described in the portmanager man page, to wit:

.if ${.CURDIR:M*/mail/p5-Mail-SpamAssassin}
WITH_SPF_QUERY=1
WITH_MYSQL=1
WITH_TOOLS=1
USE_SQLDB=1
.endif

This allows you to use different make optins depending for each port if
you wish.

-- 
Danny MacMillan




More information about the freebsd-ports mailing list