pkgsrc/mail/nullmailer, branch pkgsrc-2011Q2 [no description] https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc-2011Q2 2009-10-23T02:43:52Z Distfile changed in place, set DIST_SUBDIR (noticed by taca@). 2009-10-23T02:43:52Z schmonz schmonz@pkgsrc.org 2009-10-23T02:43:52Z urn:sha1:7ee9fbd02453b9b69512a72a9ad7e13a31808b08 Update to 1.05. From the changelog: 2009-10-21T15:06:46Z schmonz schmonz@pkgsrc.org 2009-10-21T15:06:46Z urn:sha1:44c3710e66493316e15846848b856e5b25303fba - Fixed compilation of src/selfpipe.cc on Solaris and other OSes. - Fixed handling of TM_HAS_ISDST on Solaris. - Fixed a few address parsing glitches. fix the DESTDIR support by removing the install-root target which 2009-10-14T21:13:41Z plunky plunky@pkgsrc.org 2009-10-14T21:13:41Z urn:sha1:e6e0d17e6fc3e0bf55c96ad251449f39b1c33281 would otherwise cause a chown of the trigger file. (with DESTDIR, the "nullmail" user & group are not yet created) Because this leaves the trigger file possibly owned by root, add a test in the rc "start" path to [re]make it when necessary. put this test and the daemon background and logging into a separate script so that it can be run by the rc framework as the nullmail user in the normal way, and add a procname argument to allow the "status" and "stop" rc commands to work properly. bump PKGREVISION disable DESTDIR support. There is an issue with adding the 'nullmail' 2009-10-13T13:55:28Z plunky plunky@pkgsrc.org 2009-10-13T13:55:28Z urn:sha1:c84a08e08aeb5d961d2a8ddaab93cc5074f350e9 user and using chown nullmail:nullmail that I'm looking into update to nullmailer-1.04 2009-10-11T10:25:24Z plunky plunky@pkgsrc.org 2009-10-11T10:25:24Z urn:sha1:8e156c9e813c098e038b4ef5f7f3a31bacefb981 while here, fix some pkglint complaints, add DESTDIR support and provide a LICENCE fix a problem with the rc script where the command would not start 2009-10-11T10:22:51Z plunky plunky@pkgsrc.org 2009-10-11T10:22:51Z urn:sha1:75d1765a4fbf7c364e82b796cfd4190bf46c365a at boot time. This is because the & is within the command_args string. use a start_cmd instead. Remove @dirrm entries from PLISTs 2009-06-14T18:03:28Z joerg joerg@pkgsrc.org 2009-06-14T18:03:28Z urn:sha1:24151e2b9991726fa4bcd0ace9289f45de0f325e set permissions on the fifo when we make the fifo rather than using 2007-11-26T08:27:24Z plunky plunky@pkgsrc.org 2007-11-26T08:27:24Z urn:sha1:7f623d9f3355f7f115a51cd249797dbbeacfd1ff SPECIAL_PERMS because ordering seems to be an issue Make it easier to build and install packages "unprivileged", where 2007-07-04T20:54:31Z jlam jlam@pkgsrc.org 2007-07-04T20:54:31Z urn:sha1:4390d56940778d6ab856866401c0690f1c28c724 the owner of all installed files is a non-root user. This change affects most packages that require special users or groups by making them use the specified unprivileged user and group instead. (1) Add two new variables PKG_GROUPS_VARS and PKG_USERS_VARS to unprivileged.mk. These two variables are lists of other bmake variables that define package-specific users and groups. Packages that have user-settable variables for users and groups, e.g. apache and APACHE_{USER,GROUP}, courier-mta and COURIER_{USER,GROUP}, etc., should list these variables in PKG_USERS_VARS and PKG_GROUPS_VARS so that unprivileged.mk can know to set them to ${UNPRIVILEGED_USER} and ${UNPRIVILEGED_GROUP}. (2) Modify packages to use PKG_GROUPS_VARS and PKG_USERS_VARS. Do SUBST_SED in post-configure rather than post-patch to ease patch 2007-03-24T06:49:02Z schmonz schmonz@pkgsrc.org 2007-03-24T06:49:02Z urn:sha1:1582a95bb648534f0c22ea4a78ff1302ad67344d maintenance. Set INSTALLATION_DIRS appropriately. Add VARBASE to BUILD_DEFS. Fix paths in man pages.