Is this +no_startupitem variant really smart?
I recently had a request to add a +without_startupitem variant to a
port I maintain and rejected the request; since startupitems simply
enable a port to be started at boot time, but do not cause a port to
be booted at start time, it simply seems stupid to deliberately
cripple a server port such that a user would have to reinstall it if
they wanted to start the port at boot time later.
BTW: If the variant is to be retained, can it be named
+without_startupitem instead?
On 2 Mar 2007, at 16:51, [EMAIL PROTECTED] wrote:
Revision 22490 Author [EMAIL PROTECTED] Date 2007-03-02 13:51:15
-0800 (Fri, 02 Mar 2007) Log MessageAdd a +no_startupitem variant
that prevents the automatic startup of the Apache web
server.Modified Paths
trunk/dports/www/apache2/Portfile
Diff
Modified: trunk/dports/www/apache2/Portfile (22489 => 22490)---
trunk/dports/www/apache2/Portfile 2007-03-02 20:42:45 UTC (rev
22489) +++ trunk/dports/www/apache2/Portfile 2007-03-02 21:51:15
UTC (rev 22490) @@ -105,6 +105,10 @@ configure.args-append --with-
mpm=event } +variant no_startupitem { + startupitem.create no +} +
startupitem.create yes startupitem.start \ "\[ -x ${prefix}/apache2/
bin/apachectl \] && ${prefix}/apache2/bin/apachectl start > /dev/
null" @@ -112,4 +116,3 @@ "\[ -r ${prefix}/apache2/logs/httpd.pid
\] && ${prefix}/apache2/bin/apachectl stop > /dev/null"
startupitem.restart \ "\[ -r ${prefix}/apache2/logs/httpd.pid \] &&
${prefix}/apache2/bin/apachectl restart > /dev/null" -
_______________________________________________
macports-changes mailing list
[EMAIL PROTECTED]
http://lists.macosforge.org/mailman/listinfo/macports-changes
Randall Wood
[EMAIL PROTECTED]
"The rules are simple: The ball is round. The game lasts 90 minutes.
All the
rest is just philosophy."
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev
