Age | Commit message (Collapse) | Author | Files | Lines |
|
For ${OPSYS}/${USE_DESTDIR}/${PKGMANDIR} combinations that already
worked, no functional change (hence no PKGREVISION bump).
|
|
|
|
|
|
through PLIST_SUBST to the plist module.
|
|
instead of consisting of a pristine qmail tarball and netqmail
patch, 1.06 has the patch already applied. No user-visible changes
to pkgsrc, either; this just simplifies a weird build and will make
future upgrades (don't laugh!) easier.
jlam@ "looks fine"
|
|
|
|
from <URL:http://cr.yp.to/distributors.html>:
What are the distribution terms for daemontools?
2007.12.28: I hereby place the daemontools package (in particular,
daemontools-0.76.tar.gz, with MD5 checksum
1871af2453d6e464034968a0fbcb2bfc) into the public domain. The
package is no longer copyrighted.
What are the distribution terms for djbdns?
2007.12.28: I hereby place the djbdns package (in particular,
djbdns-1.05.tar.gz, with MD5 checksum 3147c5cd56832aa3b41955c7a51cbeb2)
into the public domain. The package is no longer copyrighted.
What are the distribution terms for ucspi-tcp?
2007.12.28: I hereby place the ucspi-tcp package (in particular,
ucspi-tcp-0.88.tar.gz, with MD5 checksum
39b619147db54687c4a583a7a94c9163) into the public domain. The
package is no longer copyrighted.
Am I free to modify uncopyrighted packages and distribute modified
versions?
Yes. But this does not mean that modifications are _encouraged_!
And from <URL:http://cr.yp.to/qmail/dist.html>:
I hereby place the qmail package (in particular, qmail-1.03.tar.gz,
with MD5 checksum 622f65f982e380dbe86e6574f3abcb7c) into the
public domain. You are free to modify the package, distribute
modified versions, etc.
This does not mean that modifications are encouraged!
pkgsrc will strive, as it has, to keep modifications to a tasteful
minimum. This addresses PR pkg/37964 by Aleksej Saushev.
|
|
in SPECIAL_PERMS usage.
* Consistently use 4555 for setuid and 2555 for setgid programs.
|
|
of them apply together cleanly (and thus no PKGREVISION bump). Idea
from wiz.
|
|
* Includes a generic 'MAIL FROM:' parameter parser supporting 'AUTH'
and 'SIZE' advertisements; complies to RFC 3848
* Fixes a gcc (3.4.6) -O2 optimization problem in base64.c
Bump PKGREVISION.
|
|
and remove one-line PLIST.foo files. Quote some paths to appease
pkglint. Update URL to "12 Steps to qmail List Bliss".
|
|
Patch provided by Sergey Svishchev in private mail.
|
|
rest of the SMTP logs by stripping off its unnecessary leading
'qmail-smtpd: '. Cosmetic only, no PKGREVISION bump.
|
|
on NetBSD before (and still does).
|
|
|
|
* Update qregex patch (PR pkg/34760) to 20060423:
- qregex adds the matched regex pattern to its log entries if the
LOGREGEX environment variable is set.
* Update realrcptto patch to 20061210:
- Logging uses substdio_puts() and substdio_flush() instead of
substdio_putsflush(). This makes log entries less likely to be
interleaved. Thanks to Matthew Dempsky for finding this.
- For QMAILRRTENYALL, use error code 554 after DATA, not 550.
Thanks to ... sorry, I lost track of who found this.
- Log stat() errors for .qmail files. Thanks to Chris Bensend for
suggesting this.
* Update tls-smtpauth combined patch to 20060105. TLS changes:
- bug: qmail-remote loops on malformed server response (B. Shupp,
A. Meltzer)
- no STARTTLS advertised when control/servercert.pem absent (Jason
Haar)
- control/notlshosts (Albert Weichselbraun)
- control/tlshosts/exhaustivelist
- scripts honor conf-users (Sven Verdoolaege)
- strerror declaration in tls.c compile problem (Renato Botelho,
Bill Shupp)
- chown uid.gid deprecated, should be uid:gid (Bill Shupp)
SMTP AUTH changes:
- includes the evaluation of the 'Auth' and the 'Size' parameter
in the 'Mail From:' command.
- uses DJB functions to copy FDs.
- corrects some minor mistakes displaying the 'Auth' userid.
- uses keyword "ESMTPA" in Received header in case of authentication
to comply with RFC 3848.
pkgsrc changes:
* Note SPECIAL_PERMS on qmail-queue binary (from dsainty@).
|
|
update checksums.
|
|
|
|
functional change.
|
|
be created just before its "configure" phase, obviating the need
for the hackish dependency on a qmail-users package. Since the new
functionality in bsd.pkginstall.mk also records and enforces numeric
UIDs and GIDs in binary packages, remove the note on that matter
from MESSAGE.
Bump PKGREVISION.
|
|
INSTALL/DEINSTALL script creation within pkgsrc.
If an INSTALL or DEINSTALL script is found in the package directory,
it is automatically used as a template for the pkginstall-generated
scripts. If instead, they should be used simply as the full scripts,
then the package Makefile should set INSTALL_SRC or DEINSTALL_SRC
explicitly, e.g.:
INSTALL_SRC= ${PKGDIR}/INSTALL
DEINSTALL_SRC= # emtpy
As part of the restructuring of the pkginstall framework internals,
we now *always* generate temporary INSTALL or DEINSTALL scripts. By
comparing these temporary scripts with minimal INSTALL/DEINSTALL
scripts formed from only the base templates, we determine whether or
not the INSTALL/DEINSTALL scripts are actually needed by the package
(see the generate-install-scripts target in bsd.pkginstall.mk).
In addition, more variables in the framework have been made private.
The *_EXTRA_TMPL variables have been renamed to *_TEMPLATE, which are
more sensible names given the very few exported variables in this
framework. The only public variables relating to the templates are:
INSTALL_SRC INSTALL_TEMPLATE
DEINSTALL_SRC DEINSTALL_TEMPLATE
HEADER_TEMPLATE
The packages in pkgsrc have been modified to reflect the changes in
the pkginstall framework.
|
|
|
|
|
|
|
|
INSTALLATION_DIRS takes care of it. Found by Krister's bulk build
with CHECK_FILES.
|
|
that qmail hard-codes numeric UIDs and GIDs into several binaries.
When installing a binary qmail package, you'll need to ensure that
the qmail users and groups on your system match those with which
the package was compiled.
The binary package is not (yet) redistributable. The only way you'd
get one is by making it yourself. But this allows bulk builds to
finally test all the packages that depend on qmail.
Thanks to joerg for forcing the issue (in a good way).
|
|
|
|
|
|
resolver. Convert it to the less hacky one used elsewhere, mainly
so that I won't miss it when implementing a more general solution
to this common problem.
|
|
automatically detects whether we want the pkginstall machinery to be
used by the package Makefile.
|
|
example MAKE_ENV+=FOO=${BAR} is changed to MAKE_ENV+=FOO=${BAR:Q}. Some
other changes are outlined in
http://mail-index.netbsd.org/tech-pkg/2005/12/02/0034.html
|
|
|
|
|
|
in all packages using djbware.mk. For now, keep the same default,
avoiding PKGREVISION bumps.
|
|
via PKG_OPTIONS_LEGACY_OPTS until after the next branch.
|
|
PKGSRC_USE_TOOLS go away. There is now only a single USE_TOOLS variable
that specifies all of the tools we need to build/run the package.
|
|
works on Tiger as well. No change to the patch itself.
|
|
user settable variable. Set PKG_SUGGESTED_OPTIONS instead. Also,
make use of PKG_OPTIONS_LEGACY_VARS.
Reviewed by wiz.
|
|
USE_GNU_TOOLS -> USE_TOOLS
awk -> gawk
m4 -> gm4
make -> gmake
sed -> gsed
yacc -> bison
|
|
author considers it no longer relevant. Remove the option.
|
|
|
|
INSTALLATION_DIRS rather than MAKE_DIRS. Calculate QUEUE_EXTRALEN
in a more readable fashion.
|
|
command until it is referenced within subst.mk's make targets. This
avoids needing ${EXPR} and ${WC} in the top-level make.
|
|
Reported by Robert Elz in PR 29973.
|
|
|
|
|
|
INSTALL_TARGET, rather than replacing them. This had been broken
with the introduction of djbware.mk.
|
|
define the variable containing the patch URL for the "qregex"
option. Problems noted by zuntum.
|
|
The "netqmail" PKG_OPTION to qmail is no longer enabled on Linux
by default; if you were relying on that, set it explicitly.
|
|
|