blob: 02c73f151a365e8973046e6c776e6ffee3cf1406 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
|
# $Id: PKGBUILD 101380 2013-11-24 00:43:57Z seblu $
# Maintainer: Sébastien Luttringer
# Contributor: Paul Mattal <paul@archlinux.org>
pkgname=mailman
pkgver=2.1.17
pkgrel=1
pkgdesc='The GNU Mailing List Manager'
arch=(i686 x86_64)
license=('GPL')
url='http://www.list.org/'
depends=('glibc' 'python2' 'smtp-server')
# we need to have the mailman user to build mailman
makedepends=('mailman')
# 'Defaults.py' should not be changed by users; 'mm_cfg.py' should instead.
backup=('usr/lib/mailman/Mailman/mm_cfg.py')
install=$pkgname.install
source=("http://ftp.gnu.org/gnu/$pkgname/$pkgname-$pkgver.tgz"
'mailman-2.1-build.patch'
"$pkgname.profile.sh"
"$pkgname.profile.csh"
"$pkgname.service")
md5sums=('39043257f91eb876082fa90470aa8d28'
'ed04d062379eb21e39ce1e70e6b1ade2'
'a9c71ec940c56173415fbd49087d10b0'
'85a8c30ffc444e677b286f54df530482'
'f3ea6ef02ab135274406ce52ea8bbb7b')
build() {
cd $pkgname-$pkgver
# some files in mailman doesn't use configure parameter
find . -type f -exec \
sed -i '1s,^#! \?/usr/bin/\(env \|\)python$,#!/usr/bin/python2,' {} \;
# fix directory permissions to satisfy check_perms
patch -p1 -i "$srcdir/mailman-2.1-build.patch"
# set some sane defaults before the configure script has a chance to screw them up
./configure \
--without-permcheck \
--prefix=/usr/lib/mailman \
--with-var-prefix=/var/lib/mailman \
--with-mail-gid=mailman \
--with-username=mailman \
--with-groupname=mailman \
--with-cgi-gid=http \
--with-python=/usr/bin/python2 \
--with-mailhost=localhost \
--with-urlhost=localhost
make
}
package() {
cd $pkgname-$pkgver
make DESTDIR="$pkgdir" install
# let's follow Fedora FHS way; Gentoo does it the other way round
# Create a link so that the config file mm_cfg.py appears in config
# directory /etc/mailman. We don't put mm_cfg.py in the config directory
# because its executable code (python file) and the security policy wants
# to keep executable code out of /etc and inside of a lib directory instead,
# and because traditionally mm_cfg.py was in the Mailman subdirectory and
# experienced mailman admins will expect to find it there. But having it
# "appear" in the config directory is good practice and heading in the
# right direction for FHS compliance.
install -d -m755 "$pkgdir/etc/$pkgname"
ln -sv /usr/lib/mailman/Mailman/mm_cfg.py "$pkgdir/etc/$pkgname/mm_cfg.py"
# fix some permissions to satisfy check_perms
chown -R mailman:mailman "$pkgdir"/{usr/lib/mailman,var/lib/mailman,etc/mailman/*}
chown http:mailman "$pkgdir"/var/lib/mailman/archives/private
chmod 2770 "$pkgdir"/var/lib/mailman/archives/private
chmod 2755 "$pkgdir"/usr/lib/mailman/cgi-bin/*
chmod 2755 "$pkgdir"/usr/lib/mailman/mail/mailman
cd "$srcdir"
# systemd
install -Dm 644 $pkgname.service \
"$pkgdir/usr/lib/systemd/system/$pkgname.service"
# profiles
install -Dm 755 $pkgname.profile.sh "$pkgdir/etc/profile.d/$pkgname.sh"
install -Dm 755 $pkgname.profile.csh "$pkgdir/etc/profile.d/$pkgname.csh"
}
# vim:set ts=2 sw=2 et:
|
