blob: a9a86cd0e04bdc81053b2252419e33ef4cbafd28 (
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
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
|
# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/net-zope/zope/zope-2.8.3.ebuild,v 1.1 2005/10/19 20:47:01 radek Exp $
inherit eutils multilib
DESCRIPTION="Zope is a web application platform used for building high-performance, dynamic web sites."
HOMEPAGE="http://www.zope.org"
SRC_URI="http://www.zope.org/Products/Zope/${PV}/Zope-${PV}-final.tgz"
LICENSE="ZPL"
SLOT="${PV}"
KEYWORDS="~x86 ~sparc ~ppc ~alpha ~amd64"
IUSE="unicode"
RDEPEND="=dev-lang/python-2.3*"
python='python2.3'
DEPEND="${RDEPEND}
virtual/libc
>=sys-apps/sed-4.0.5"
S="${WORKDIR}/Zope-${PV}-final"
ZUID=zope
ZGID=zope
ZS_DIR=${ROOT%/}/usr/$(get_libdir)
ZSERVDIR=${ZS_DIR}/${P}
# Narrow the scope of ownership/permissions.
# Security plan:
# * ZUID is the superuser for all zope instances.
# * ZGID is for a single instance's administration.
# * Other' should not have any access to ${ZSERVDIR},
# because they can work through the Zope web interface.
# This should protect our code/data better.
#
# UPDATE: ${ZSERVDIR} is a lib directory and should be world readable
# like e.g /usr/lib/python we do not store any user data there,
# currently removed all custom permission stuff, for ${ZSERVDIR}
src_unpack() {
unpack ${A}
cd ${S}
}
src_compile() {
./configure --ignore-largefile --prefix=. --with-python=/usr/bin/python2.3 || die "Failed to configure."
emake || die "Failed to compile."
}
src_install() {
dodoc README.txt
dodoc doc/*.txt
docinto PLATFORMS ; dodoc doc/PLATFORMS/*
docinto ZEO ; dodoc doc/ZEO/*
# Patched StructuredText will accept source text formatted in utf-8 encoding,
# apply all formattings and output utf-8 encoded text.
# if you want to use this option you need to set your
# system python encoding to utf-8 (create the file sitecustomize.py inside
# your site-packages, add the following lines
# import sys
# sys.setdefaultencoding('utf-8')
# If this is a problem, let me know right away. --batlogg@gentoo.org
# I wondering if we need a USE flag for this and wheter we can set the
# sys.encoding automtically
# so i defined a use flag
if use unicode; then
einfo "Patching structured text"
einfo "make sure you have set the system python encoding to utf-8"
einfo "create the file sitecustomize.py inside your site-packages"
einfo "import sys"
einfo "sys.setdefaultencoding('utf8')"
# stx i18n support borked. --batlogg@gentoo.org
ewarn "sorry, the Structured Text patch doesn't work yet for zope-2.8."
#cd ${S}/lib/python/StructuredText/
#epatch ${FILESDIR}/${PV}/i18n-1.0.0.patch
sleep 15
cd ${S}
fi
make install PREFIX=${D}${ZSERVDIR}
rm -rf ${D}${ZSERVDIR}/doc
dosym ../../share/doc/${PF} ${ZSERVDIR}/doc
# copy the init script skeleton to skel directory of our installation
skel=${D}${ZSERVDIR}/skel
# <radek@gentoo.org> from 2.7.4 release i think that we can use the same
# file for every one, and not separate it by PV
cp ${FILESDIR}/zope.initd ${skel}/zope.initd
}
pkg_postinst() {
# create the zope user and group for backward compatibility
enewgroup ${ZGID} 261
usermod -g ${ZGID} ${ZUID} 2>&1 >/dev/null || \
enewuser ${ZUID} 261 -1 /var/$(get_libdir)/zope ${ZGID}
einfo "Be warned that you need at least one zope instance to run zope."
einfo "Please emerge zope-config for futher instance management."
}
pkg_prerm() {
#need to remove this symlink because portage keeps links to
#existing targets
rm ${ZSERVDIR}/bin/python
}
|
GitWeb