makeinfo if no native makeinfo executable exists. Honor TEXINFO_REQD
when determining whether the native makeinfo can be used.
* Remove USE_MAKEINFO and replace it with USE_TOOLS+=makeinfo.
* Get rid of all the "split" argument deduction for makeinfo since
the PLIST module already handles varying numbers of split info files
correctly.
NOTE: Platforms that have "makeinfo" in the base system should check
that the makeinfo entries of pkgsrc/mk/tools.${OPSYS}.mk are
correct.
backslashes anymore. A single backslash is enough. Changed the
definition in all affected packages. For those that are not caught, an
additional check is placed into bsd.pkginstall.mk.
Changes of note (security fixes were already integrated in an earlier
4.4.9nbX release):
* src/gate/ftn2rfc.c (unpack): if * Origin is empty, don't use it
for the Organization header, use default from config.
* src/common/log.c (logit): renamed old log() to avoid conflict
with Standard-C math function.
* src/common/log.c (log_program): removed insecure code entirely,
thanks to Niels Heinen for pointing this out.
* src/gate/send-fidogate.sh: added optimized version using rfc2ftn
-f for INN 2.4, thanks to Viktor Kafke.
Optimized versions for INN 2.2 und INN 2.4 enabled by
OPTIMIZED=yes at the start of this script, default = commented =
off.
* scripts/maintenance/logsendmail2.pl: new version of logsendmail
utility.
* src/gate/rfc2ftn.c (receiver): "sysop" is always a valid name.
* src/gate/rfc2ftn.c (main): new option "SilentBounces" causes
EX_NOHOST, EX_NOUSER errors to return OK without any message.
Useful in the never ending fight against spam, when your gateway
is flooded with messages to unknown adresses, such as Fido.DE :-(
(snd_mail): check silent_bounces, if set return OK and log only.
And always is defined as share/examples/rc.d
which was the default before.
This rc.d scripts are not automatically added to PLISTs now also.
So add to each corresponding PLIST as required.
This was discussed on tech-pkg in late January and late April.
Todo: remove the RCD_SCRIPTS_EXAMPLEDIR uses in MESSAGES and elsewhere
and remove the RCD_SCRIPTS_EXAMPLEDIR itself.
under share/examples/rc.d. The variable name already was named
RCD_SCRIPTS_EXAMPLEDIR.
This is from ideas from Greg Woods and others.
Also bumped PKGREVISION for all packages using RCD_SCRIPTS mechanism
(as requested by wiz).
under ${PREFIX} instead of being an absolute path.
So fix the references using RCD_SCRIPTS_EXAMPLEDIR to be
${PREFIX}/${RCD_SCRIPTS_EXAMPLEDIR}.
This should have no changes to use before.
Please note that the MESSAGE files in most cases are wrong in the
first place. We have automated mechanisms and could have an automated
message for explaining rc.d script usage. (This is something to do!)
changes local to the author's system and changes in doc to note better
the newer home on SourceForge.
However, this does contain a quasi-security fix: LOGFILE and
FIDOGATE_LOGFILE could have been used to alter files owned by user/group
"news". This is fixed in 4.4.9nb1, and will also be fixed in 4.4.10 from
the author.
the RCD_SCRIPTS rc.d script(s) to the PLIST.
This GENERATE_PLIST idea is part of Greg A. Woods'
PR #22954.
This helps when the RC_SCRIPTS are installed to
a different ${RCD_SCRIPTS_EXAMPLEDIR}. (Later,
the default RCD_SCRIPTS_EXAMPLEDIR will be changed
to be more clear that they are the examples.)
These patches also remove the etc/rc.d/ scripts from PLISTs
(of packages that use RCD_SCRIPTS). (This also removes
now unused references from openssh* makefiles. Note that
qmail package has not been changed yet.)
I have been doing automatic PLIST registration for RC_SCRIPTS
for over a year. Not all of these packages have been tested,
but many have been tested and used.
Somethings maybe to do:
- a few packages still manually install the rc.d scripts to
hard-coded etc/rc.d. These need to be fixed.
- maybe remove from mk/${OPSYS}.pkg.dist mtree specifications too.
have it be automatically included by bsd.pkg.mk if USE_PKGINSTALL is set
to "YES". This enforces the requirement that bsd.pkg.install.mk be
included at the end of a package Makefile. Idea suggested by Julio M.
Merino Vidal <jmmv at menta.net>.
