literal name_enable wherever possible, and ${name}_enable
when it's not, to prepare for the demise of set_rcvar().
In cases where I had to hand-edit unusual instances also
modify formatting slightly to be more uniform (and in
some cases, correct). This includes adding some $FreeBSD$
tags, and most importantly moving rcvar= to right after
name= so it's clear that one is derived from the other.
- Name
em@i.l
or variations thereof. While I'm here also fix some whitespace and other
formatting errors, including moving WWW: to the last line in the file.
propogated by copy and paste.
1. Primarily the "empty variable" default assignment, which is mostly
${name}_flags="", but fix a few others as well.
2. Where they are not already documented, add the existence of the _flags
(or other deleted empties) option to the comments, and in some cases add
comments from scratch.
3. Replace things that look like:
prefix=%%PREFIX%%
command=${prefix}/sbin/foo
to just use %%PREFIX%%. In many cases the $prefix variable is only used
once, and in some cases it is not used at all.
4. In a few cases remove ${name}_flags from command_args
5. Remove a long-stale comment about putting the port's rc.d script in
/etc/rc.d (which is no longer necessary).
No PORTREVISION bumps because all of these changes are noops.
- Change default value assignment in rc script to match Porter's Handbook [2]
- Use GNU_CONFIGURE as the configure script is generated by autoconf [2]
PR: ports/115652 [1]
Submitted by: Max E. Kuznecov <mek at mek.uz.ua> (maintainer) [1]
Approved by: Max E. Kuznecov <mek at mek.uz.ua> (maintainer) [2]
We have not checked for this KEYWORD for a long time now, so this
is a complete noop, and thus no PORTREVISION bump. Removing it at
this point is mostly for pedantic reasons, and partly to avoid
perpetuating this anachronism by copy and paste to future scripts.
- Convert to OPTIONS [1]
- Use %%DATADIR%% [2]
- Add a hint to UPDATING because of changed config file semantics. [1]
Submitted by: maintainer [1],
barner [2]
PR: ports/81375
Blizzard Battle.net server. It currently supports all Battle.net games, such as
StarCraft, Diablo II, and Warcraft III, and gives you the power to run your own
server, manage your own users, run your own tournaments, etc.
PR: ports/76445
Submitted by: Max E. Kuznecov <mek@mek.uz.ua>
