| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
automatically by pthread.buildlink3.mk. Also, factor out the pthread
library out of PTHREAD_LDFLAGS into a standalone variable PTHREAD_LIBS
and use it in packages where necessary (usually the ones that don't
have a GNU configure script).
|
|
|
|
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.
|
|
o Fixes to make building and installing more easy
o Make MaraDNS actually look into ${PKG_SYSCONFDIR} for its configuration
file, thus bumping PKGREVISION.
|
|
|
|
|
|
(Note that anyway, maradns' installation process is screwed up. It uses
cp and mkdir to install things, it copies useless stuff like Makefiles,
installs duplicates of manpages, etc...)
|
|
Changes:
Cleaned up and fixed a bug in the MaraDNS startup
script. Now, the only prorcesses that will be killed
will be bona fide MaraDNS processes.
Closes PR pkg/22963.
|
|
Package provided by pancake <pancake@phreaker.net> via pkgsrc-wip.
MaraDNS is a package that implements the Domain Name Service (DNS), an
essential internet service. MaraDNS is intended for environments where a DNS
server must be secure and where the server must use the absolute minimum
number of resources possible. MaraDNS was created in response to issues
people had with the DNS servers available in early 2001; and has the
following design goals:
Security-aware programming. A DNS server needs to be secure. I have a number
of security features in the code, including:
1. The code uses a special string library which is resistant to buffer
overflows.
2. The code, if started as root, mandates running as an unpriviledged user
in a chroot() jail.
Open-Source. The 1.0 release of the DNS server is public-domain code;
the 1.2 release will be released under a very liberal BSD-style license.
Simplicity. This DNS server has the minimum number of features needed to
correctly act as an authoritative and/or recursive name server.
|
