Re: apache 2.2.22_8
On Sat, Sep 15, 2012 at 8:30 PM, Solmin Vladimir v...@celicom.ru wrote:
Hi!
Im using apache 2.2.22_6 with make options in /etc/make.conf
# apache22
.if ${.CURDIR} == ${PORTSDIR}/www/apache22
WITH_SUEXEC=YES
SUEXEC_DOCROOT= /www
SUEXEC_USERDIR= /www/*/cgi-bin
SUEXEC_LOGFILE= /var/log/suexec.log
WITH_APACHE_PERF_TUNING=yes
.endif
But after svn co /usr/ports today i'm see next:
$portupgrade -arR
** Port marked as IGNORE: www/apache22:
is marked as broken: WITH/WITHOUT parameters are obsolete. The
port use the new options NG framework. Please read
http://wiki.freebsd.org/Ports/**Options/OptionsNGhttp://wiki.freebsd.org/Ports/Options/OptionsNG
but a don't understand how i must set SUEXEC_DOCROOT, SUEXEC_USERDIR and
SUEXEC_LOGFILE in NG framework format...
Please help show me how
I have read that instruction and I am also not clear with what the correct
syntax is for /etc/make.conf.
I have come up with this:
# apache22
.if ${.CURDIR} == ${PORTSDIR}/www/apache22
${APACHE22}_SET=SUEXEC
${APACHE22}_SET=SUEXEC_DOCROOT /www
${APACHE22}_SET=SUEXEC_USERDIR /www/*/cgi-bin
${APACHE22}_SET=SUEXEC_LOGFILE /var/log/suexec.log
.endif
I cant say if that's how it should be, but I think:-)
Hopefully, Chris can help us understand the syntax better.
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
I can't hear you -- I'm using the scrambler.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: apache 2.2.22_8
On 16 September 2012 07:19, Odhiambo Washington odhia...@gmail.com wrote:
On Sat, Sep 15, 2012 at 8:30 PM, Solmin Vladimir v...@celicom.ru wrote:
Hi!
Im using apache 2.2.22_6 with make options in /etc/make.conf
# apache22
.if ${.CURDIR} == ${PORTSDIR}/www/apache22
WITH_SUEXEC=YES
SUEXEC_DOCROOT= /www
SUEXEC_USERDIR= /www/*/cgi-bin
SUEXEC_LOGFILE= /var/log/suexec.log
WITH_APACHE_PERF_TUNING=yes
.endif
But after svn co /usr/ports today i'm see next:
$portupgrade -arR
** Port marked as IGNORE: www/apache22:
is marked as broken: WITH/WITHOUT parameters are obsolete. The
port use the new options NG framework. Please read
http://wiki.freebsd.org/Ports/Options/OptionsNG
but a don't understand how i must set SUEXEC_DOCROOT, SUEXEC_USERDIR and
SUEXEC_LOGFILE in NG framework format...
Please help show me how
I have read that instruction and I am also not clear with what the correct
syntax is for /etc/make.conf.
I have come up with this:
# apache22
.if ${.CURDIR} == ${PORTSDIR}/www/apache22
${APACHE22}_SET=SUEXEC
${APACHE22}_SET=SUEXEC_DOCROOT /www
${APACHE22}_SET=SUEXEC_USERDIR /www/*/cgi-bin
${APACHE22}_SET=SUEXEC_LOGFILE /var/log/suexec.log
.endif
I cant say if that's how it should be, but I think:-)
Hopefully, Chris can help us understand the syntax better.
Thanks for copying me in, I'm not on this list.
You're very close!
You need to use ${UNIQUENAME}_SET, and to find the UNIQUENAME you need to;
[crees@pegasus]~% cd /usr/ports/www/apache22
[crees@pegasus]/usr/ports/www/apache22% make -VUNIQUENAME
apache22
Now we know it's apache22, we can use:
# (No need to bother with .if ${.CURDIR} any more)
apache22_SET+= SUEXEC
SUEXEC_DOCROOT= /www
SUEXEC_USERDIR= /www/*/cgi-bin
SUEXEC_LOGFILE= /var/log/suexec.log
I'm not sure what APACHE_PERF_TUNING is; you may find it's been
deprecated. Check with apache@ about that. If I've somehow missed
that, you can just add it to the apache22_SET list:
apache22_SET+= SUEXEC APACHE_PERF_TUNING
Hope that helps!
Chris
(corresponding to WITHOUT is ${UNIQUENAME}_UNSET)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: apache 2.2.22_8
Hi Chris,
Thanks for this.
Hopefully, you can modify the Wiki to have this information and even
examples:)
Personally, I use `make config` and have never needed to do much with
/etc/make.conf as regards the ports.
On Sun, Sep 16, 2012 at 11:17 AM, Chris Rees cr...@freebsd.org wrote:
On 16 September 2012 07:19, Odhiambo Washington odhia...@gmail.com
wrote:
On Sat, Sep 15, 2012 at 8:30 PM, Solmin Vladimir v...@celicom.ru wrote:
Hi!
Im using apache 2.2.22_6 with make options in /etc/make.conf
# apache22
.if ${.CURDIR} == ${PORTSDIR}/www/apache22
WITH_SUEXEC=YES
SUEXEC_DOCROOT= /www
SUEXEC_USERDIR= /www/*/cgi-bin
SUEXEC_LOGFILE= /var/log/suexec.log
WITH_APACHE_PERF_TUNING=yes
.endif
But after svn co /usr/ports today i'm see next:
$portupgrade -arR
** Port marked as IGNORE: www/apache22:
is marked as broken: WITH/WITHOUT parameters are obsolete. The
port use the new options NG framework. Please read
http://wiki.freebsd.org/Ports/Options/OptionsNG
but a don't understand how i must set SUEXEC_DOCROOT, SUEXEC_USERDIR and
SUEXEC_LOGFILE in NG framework format...
Please help show me how
I have read that instruction and I am also not clear with what the
correct
syntax is for /etc/make.conf.
I have come up with this:
# apache22
.if ${.CURDIR} == ${PORTSDIR}/www/apache22
${APACHE22}_SET=SUEXEC
${APACHE22}_SET=SUEXEC_DOCROOT /www
${APACHE22}_SET=SUEXEC_USERDIR /www/*/cgi-bin
${APACHE22}_SET=SUEXEC_LOGFILE /var/log/suexec.log
.endif
I cant say if that's how it should be, but I think:-)
Hopefully, Chris can help us understand the syntax better.
Thanks for copying me in, I'm not on this list.
You're very close!
You need to use ${UNIQUENAME}_SET, and to find the UNIQUENAME you need to;
[crees@pegasus]~% cd /usr/ports/www/apache22
[crees@pegasus]/usr/ports/www/apache22% make -VUNIQUENAME
apache22
Now we know it's apache22, we can use:
# (No need to bother with .if ${.CURDIR} any more)
apache22_SET+= SUEXEC
SUEXEC_DOCROOT= /www
SUEXEC_USERDIR= /www/*/cgi-bin
SUEXEC_LOGFILE= /var/log/suexec.log
I'm not sure what APACHE_PERF_TUNING is; you may find it's been
deprecated. Check with apache@ about that. If I've somehow missed
that, you can just add it to the apache22_SET list:
apache22_SET+= SUEXEC APACHE_PERF_TUNING
Hope that helps!
Chris
(corresponding to WITHOUT is ${UNIQUENAME}_UNSET)
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
I can't hear you -- I'm using the scrambler.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: apache 2.2.22_8
On 16 September 2012 09:32, Odhiambo Washington odhia...@gmail.com wrote:
Hi Chris,
Thanks for this.
Hopefully, you can modify the Wiki to have this information and even
examples:)
There are examples on the Wiki page already, but in a confusing order.
I've put in a link, and a tip on how to find UNIQUENAME.
Personally, I use `make config` and have never needed to do much with
/etc/make.conf as regards the ports.
True, but some people like to share their make.conf around machines :)
Chris
On Sun, Sep 16, 2012 at 11:17 AM, Chris Rees cr...@freebsd.org wrote:
On 16 September 2012 07:19, Odhiambo Washington odhia...@gmail.com
wrote:
On Sat, Sep 15, 2012 at 8:30 PM, Solmin Vladimir v...@celicom.ru wrote:
Hi!
Im using apache 2.2.22_6 with make options in /etc/make.conf
# apache22
.if ${.CURDIR} == ${PORTSDIR}/www/apache22
WITH_SUEXEC=YES
SUEXEC_DOCROOT= /www
SUEXEC_USERDIR= /www/*/cgi-bin
SUEXEC_LOGFILE= /var/log/suexec.log
WITH_APACHE_PERF_TUNING=yes
.endif
But after svn co /usr/ports today i'm see next:
$portupgrade -arR
** Port marked as IGNORE: www/apache22:
is marked as broken: WITH/WITHOUT parameters are obsolete. The
port use the new options NG framework. Please read
http://wiki.freebsd.org/Ports/Options/OptionsNG
but a don't understand how i must set SUEXEC_DOCROOT, SUEXEC_USERDIR
and
SUEXEC_LOGFILE in NG framework format...
Please help show me how
I have read that instruction and I am also not clear with what the
correct
syntax is for /etc/make.conf.
I have come up with this:
# apache22
.if ${.CURDIR} == ${PORTSDIR}/www/apache22
${APACHE22}_SET=SUEXEC
${APACHE22}_SET=SUEXEC_DOCROOT /www
${APACHE22}_SET=SUEXEC_USERDIR /www/*/cgi-bin
${APACHE22}_SET=SUEXEC_LOGFILE /var/log/suexec.log
.endif
I cant say if that's how it should be, but I think:-)
Hopefully, Chris can help us understand the syntax better.
Thanks for copying me in, I'm not on this list.
You're very close!
You need to use ${UNIQUENAME}_SET, and to find the UNIQUENAME you need to;
[crees@pegasus]~% cd /usr/ports/www/apache22
[crees@pegasus]/usr/ports/www/apache22% make -VUNIQUENAME
apache22
Now we know it's apache22, we can use:
# (No need to bother with .if ${.CURDIR} any more)
apache22_SET+= SUEXEC
SUEXEC_DOCROOT= /www
SUEXEC_USERDIR= /www/*/cgi-bin
SUEXEC_LOGFILE= /var/log/suexec.log
I'm not sure what APACHE_PERF_TUNING is; you may find it's been
deprecated. Check with apache@ about that. If I've somehow missed
that, you can just add it to the apache22_SET list:
apache22_SET+= SUEXEC APACHE_PERF_TUNING
Hope that helps!
Chris
(corresponding to WITHOUT is ${UNIQUENAME}_UNSET)
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
I can't hear you -- I'm using the scrambler.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: apache 2.2.22_8
On Sun, Sep 16, 2012 at 11:47 AM, Chris Rees cr...@freebsd.org wrote: On 16 September 2012 09:32, Odhiambo Washington odhia...@gmail.com wrote: Hi Chris, Thanks for this. Hopefully, you can modify the Wiki to have this information and even examples:) There are examples on the Wiki page already, but in a confusing order. I've put in a link, and a tip on how to find UNIQUENAME. Personally, I use `make config` and have never needed to do much with /etc/make.conf as regards the ports. True, but some people like to share their make.conf around machines :) Chris My machines are all identical too, except for parameters related to $hostname, DNS and passwords. I mostly used /usr/local/etc/pkgtools.conf before, then `make config` and now I believe I am gonna switch to /etc/make.conf but only where I must finely customize. One thing has crossed my mind now: What happens with make -DWITH_* in this new development of optionsNG?? I have manually built ports that way before. And what about those who want to use portinstall -m WITH_OPTx=1 WITH_OPTy=1, etc? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ I can't hear you -- I'm using the scrambler. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: apache 2.2.22_8
On 16 September 2012 10:20, Odhiambo Washington odhia...@gmail.com wrote: On Sun, Sep 16, 2012 at 11:47 AM, Chris Rees cr...@freebsd.org wrote: On 16 September 2012 09:32, Odhiambo Washington odhia...@gmail.com wrote: Hi Chris, Thanks for this. Hopefully, you can modify the Wiki to have this information and even examples:) There are examples on the Wiki page already, but in a confusing order. I've put in a link, and a tip on how to find UNIQUENAME. Personally, I use `make config` and have never needed to do much with /etc/make.conf as regards the ports. True, but some people like to share their make.conf around machines :) Chris My machines are all identical too, except for parameters related to $hostname, DNS and passwords. I mostly used /usr/local/etc/pkgtools.conf before, then `make config` and now I believe I am gonna switch to /etc/make.conf but only where I must finely customize. One thing has crossed my mind now: What happens with make -DWITH_* in this new development of optionsNG?? I have manually built ports that way before. And what about those who want to use portinstall -m WITH_OPTx=1 WITH_OPTy=1, etc? Still works fine for nearly all ports, but just for apache ports there appears to be subtle problems with the logic since it's so complicated. That's why Olli chose to disable the WITH_ option style for Apache, and I think it was the right decision. I would suggest you learn the new (just as simple) syntax and see how you get on with it :) Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: apache 2.2.22_8
On Sun, Sep 16, 2012 at 12:25 PM, Chris Rees cr...@freebsd.org wrote: On 16 September 2012 10:20, Odhiambo Washington odhia...@gmail.com wrote: On Sun, Sep 16, 2012 at 11:47 AM, Chris Rees cr...@freebsd.org wrote: On 16 September 2012 09:32, Odhiambo Washington odhia...@gmail.com wrote: Hi Chris, Thanks for this. Hopefully, you can modify the Wiki to have this information and even examples:) There are examples on the Wiki page already, but in a confusing order. I've put in a link, and a tip on how to find UNIQUENAME. Personally, I use `make config` and have never needed to do much with /etc/make.conf as regards the ports. True, but some people like to share their make.conf around machines :) Chris My machines are all identical too, except for parameters related to $hostname, DNS and passwords. I mostly used /usr/local/etc/pkgtools.conf before, then `make config` and now I believe I am gonna switch to /etc/make.conf but only where I must finely customize. One thing has crossed my mind now: What happens with make -DWITH_* in this new development of optionsNG?? I have manually built ports that way before. And what about those who want to use portinstall -m WITH_OPTx=1 WITH_OPTy=1, etc? Still works fine for nearly all ports, but just for apache ports there appears to be subtle problems with the logic since it's so complicated. That's why Olli chose to disable the WITH_ option style for Apache, and I think it was the right decision. I would suggest you learn the new (just as simple) syntax and see how you get on with it :) Chris I was thinking this optionsNG has already been adopted for all ports. Thanks for the examples though. They are good enough for me to learn the ropes.. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ I can't hear you -- I'm using the scrambler. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: apache 2.2.22_8
On 16 September 2012 10:37, Odhiambo Washington odhia...@gmail.com wrote: On Sun, Sep 16, 2012 at 12:25 PM, Chris Rees cr...@freebsd.org wrote: On 16 September 2012 10:20, Odhiambo Washington odhia...@gmail.com wrote: On Sun, Sep 16, 2012 at 11:47 AM, Chris Rees cr...@freebsd.org wrote: On 16 September 2012 09:32, Odhiambo Washington odhia...@gmail.com wrote: Hi Chris, Thanks for this. Hopefully, you can modify the Wiki to have this information and even examples:) There are examples on the Wiki page already, but in a confusing order. I've put in a link, and a tip on how to find UNIQUENAME. Personally, I use `make config` and have never needed to do much with /etc/make.conf as regards the ports. True, but some people like to share their make.conf around machines :) Chris My machines are all identical too, except for parameters related to $hostname, DNS and passwords. I mostly used /usr/local/etc/pkgtools.conf before, then `make config` and now I believe I am gonna switch to /etc/make.conf but only where I must finely customize. One thing has crossed my mind now: What happens with make -DWITH_* in this new development of optionsNG?? I have manually built ports that way before. And what about those who want to use portinstall -m WITH_OPTx=1 WITH_OPTy=1, etc? Still works fine for nearly all ports, but just for apache ports there appears to be subtle problems with the logic since it's so complicated. That's why Olli chose to disable the WITH_ option style for Apache, and I think it was the right decision. I would suggest you learn the new (just as simple) syntax and see how you get on with it :) Chris I was thinking this optionsNG has already been adopted for all ports. Thanks for the examples though. They are good enough for me to learn the ropes.. Both syntaxes will work with old and new-style port OPTIONS. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: apache 2.2.22_8
On Sun, 16 Sep 2012 09:17:55 +0100
Chris Rees articulated:
You need to use ${UNIQUENAME}_SET, and to find the UNIQUENAME you
need to;
[crees@pegasus]~% cd /usr/ports/www/apache22
[crees@pegasus]/usr/ports/www/apache22% make -VUNIQUENAME
apache22
Now we know it's apache22, we can use:
I tried this with postfix and the postfix-current port and both
returned the same unique name. Is that to be expected? I would have
though that two different ports would return different unique names.
--
Jerry ♔
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__
The trouble with a lot of self-made men is that they worship their
creator.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
apache 2.2.22_8
Hi!
Im using apache 2.2.22_6 with make options in /etc/make.conf
# apache22
.if ${.CURDIR} == ${PORTSDIR}/www/apache22
WITH_SUEXEC=YES
SUEXEC_DOCROOT= /www
SUEXEC_USERDIR= /www/*/cgi-bin
SUEXEC_LOGFILE= /var/log/suexec.log
WITH_APACHE_PERF_TUNING=yes
.endif
But after svn co /usr/ports today i'm see next:
$portupgrade -arR
** Port marked as IGNORE: www/apache22:
is marked as broken: WITH/WITHOUT parameters are obsolete. The
port use the new options NG framework. Please read
http://wiki.freebsd.org/Ports/Options/OptionsNG
but a don't understand how i must set SUEXEC_DOCROOT, SUEXEC_USERDIR and
SUEXEC_LOGFILE in NG framework format...
Please help show me how
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
