Solved The annoying struggle of updating ports

[Leander]

Hi

the most only reasons why I don't look forward updating the ports is the uneccesarry struggle of WWWDIR. All Ports which sort of make use of this must be individually re-installed and re-configured as well as re-arranged manually again. Why? Because the default /usr/local/www/$PORTNAME and /usr/local/www/cgi-dir/$PORTNAME schema does not apply to my very well for my needs setup http-environment. Instead of the default, my optimized vHost environment looks like this: /usr/local/www/nut.hostname.tld/sites and the other relevant to this post: /usr/local/www/nut.hostname.tld/sites.

I'm aware of the global variable WWWDIR for make.conf - yet this is a global var applying to all ports. Instead I'm looking for port specific variables for HTML and CGI relevant files. Is there anything sustainable you can recomment? I don't want to manually change Makefiles each time update the ports three - this would not be sustainable. Goal would be more something like this:

sysutils_nut_SET=BASH CGI CGIDIR=/usr/local/www/nut.hostname.tld/cgi-bin/nut WWWDIR=/usr/local/www/nut.hostname.tld/sites
sysutils_nut_UNSET=SERIAL USB

Thanks

 

[kpa]

There is this trick from the example make.conf(5) at /usr/share/examples/etc/make.conf:

.if ${.CURDIR:M*/sysutils/nut}
CGIDIR=/...
WWWDIR=/...
.endif

 

[Leander]

Thanks for your reply. I'm well aware of this example, but I'm a little puzzled now. I thought it is highly depreciated to use your suggested example anylonger, since it has been replaced by the syntax:

[noparse][CATEGORY]_[PORT]_[SET|UNSET]=OPTION1 OPTION2 ...[/noparse]

 

[kpa]

Thanks for your reply. I'm well aware of this example, but I'm a little puzzled now. I thought it is highly depreciated to use your suggested example anylonger, since it has been replaced by the syntax: "[CATEGORY]__[SET|UNSET]=OPTION1 OPTION2 ..." ?!

No it's not deprecated at all, the syntax you're quoting is only for setting/unsetting defined options that you can set/unset with make config. Any other knobs with values other than YES/NO have to be set without any prefixes because the ports infrastructure doesn't yet make those knobs available for assignment in the new syntax (probably won't be available at all, the prefix is what implies the value and it's limited to set/unset now).

 

[Leander]

All right - thanks for the clarification.