summaryrefslogtreecommitdiff
path: root/mail/alpine
diff options
context:
space:
mode:
authorplunky <plunky@pkgsrc.org>2009-05-17 17:34:01 +0000
committerplunky <plunky@pkgsrc.org>2009-05-17 17:34:01 +0000
commit0c9396462dcd5b0cb91aa19dca9167b75124ebd6 (patch)
treedb3225ce080f471e834ae64643842f3908f621d8 /mail/alpine
parentc6218863df45455e89af911947978991f0b4cd6d (diff)
downloadpkgsrc-0c9396462dcd5b0cb91aa19dca9167b75124ebd6.tar.gz
include <time.h> and <utime.h> so that where time_t has been changed to 64-bit
values on NetBSD, we we get correctly referred to __utime50() which can handle 64-bit values. This fixes a problem where mailbox mtimes were being reset to 0 Note that this actually causes some build warnings as the code uses "time_t tp[2]" instead of "struct utimbuf tp" (contains two time_t values) Although the <os_bsi.h> file says it is used for BSDI, it seems to be used by NetBSD and OpenBSD, both of which have the <utime.h> and <time.h> bump PKGREVISION
Diffstat (limited to 'mail/alpine')
-rw-r--r--mail/alpine/Makefile4
-rw-r--r--mail/alpine/distinfo3
-rw-r--r--mail/alpine/patches/patch-aa25
3 files changed, 29 insertions, 3 deletions
diff --git a/mail/alpine/Makefile b/mail/alpine/Makefile
index 0b7094e48fc..d55cc6f0442 100644
--- a/mail/alpine/Makefile
+++ b/mail/alpine/Makefile
@@ -1,8 +1,8 @@
-# $NetBSD: Makefile,v 1.19 2009/05/01 11:58:46 abs Exp $
+# $NetBSD: Makefile,v 1.20 2009/05/17 17:34:01 plunky Exp $
#
DISTNAME= alpine-2.00
-PKGREVISION= 1
+PKGREVISION= 2
CATEGORIES= mail
MASTER_SITES= ftp://ftp.cac.washington.edu/alpine/
DIST_SUBDIR= alpine-2.00
diff --git a/mail/alpine/distinfo b/mail/alpine/distinfo
index bf12b19b8ef..3c2f1358ed6 100644
--- a/mail/alpine/distinfo
+++ b/mail/alpine/distinfo
@@ -1,4 +1,4 @@
-$NetBSD: distinfo,v 1.14 2009/05/01 11:58:46 abs Exp $
+$NetBSD: distinfo,v 1.15 2009/05/17 17:34:01 plunky Exp $
SHA1 (alpine-2.00/alpine-2.00.tar.bz2) = dcbd3c5419954f484ccf706feaba31ce48cdebc4
RMD160 (alpine-2.00/alpine-2.00.tar.bz2) = 9e67704b23b3973d8b878e65ad9e6f5026c10d13
@@ -12,3 +12,4 @@ Size (alpine-2.00/maildir.patch.gz) = 32100 bytes
SHA1 (alpine-2.00/searchheader.patch.gz) = 1c8dfaefa9a9ed502da454b5d1334c94bc1873c4
RMD160 (alpine-2.00/searchheader.patch.gz) = cc1b2c3cf4cbceaf62e1c0378f5edf6bee619581
Size (alpine-2.00/searchheader.patch.gz) = 1708 bytes
+SHA1 (patch-aa) = c306613a297d61591d577b6968a31fc85b03f852
diff --git a/mail/alpine/patches/patch-aa b/mail/alpine/patches/patch-aa
new file mode 100644
index 00000000000..4d75d6626c4
--- /dev/null
+++ b/mail/alpine/patches/patch-aa
@@ -0,0 +1,25 @@
+$NetBSD: patch-aa,v 1.4 2009/05/17 17:34:01 plunky Exp $
+
+include <time.h> and <utime.h> so that where time_t has been changed to 64-bit
+values on NetBSD, we we get correctly referred to __utime50() which can handle
+64-bit values. This fixes a problem where mailbox mtimes were being reset to 0
+
+Note that this actually causes some build warnings as the code uses
+"time_t tp[2]" instead of "struct utimbuf tp" (contains two time_t values)
+
+Although the <os_bsi.h> file says it is used for BSDI, it seems to be used by
+NetBSD and OpenBSD, both of which have the <utime.h> and <time.h>
+
+ - plunky
+
+--- imap/src/osdep/unix/os_bsi.h.orig 2008-06-04 19:18:34.000000000 +0100
++++ imap/src/osdep/unix/os_bsi.h 2009-05-17 18:00:44.000000000 +0100
+@@ -34,6 +34,8 @@
+ #include <fcntl.h>
+ #include <syslog.h>
+ #include <sys/file.h>
++#include <time.h>
++#include <utime.h>
+
+
+ #include "env_unix.h"