mirror of
https://git.freebsd.org/ports.git
synced 2025-07-18 09:49:18 -04:00
Initial import of zope version 2.0.0b5.
An object-based web application platform with database access. PR: 13324 Submitted by: Peter Cornelius <pcc@gmx.net>
This commit is contained in:
Steve Price
parent
ea9fb84528
commit
f73c0fc047
Notes:
svn2git
2021-03-31 03:12:20 +00:00
svn path=/head/; revision=22798
42 changed files with 7680 additions and 0 deletions
82
www/zope/Makefile
Normal file
82
www/zope/Makefile
Normal file
|
|
@ -0,0 +1,82 @@
|
|||
# New ports collection makefile for: Zope
|
||||
# Version required: 2.0.1
|
||||
# Date created: Sat 21 Aug 1999
|
||||
# Whom: Peter Cornelius <pcc@gmx.net>
|
||||
#
|
||||
# $FreeBSD$
|
||||
|
||||
DISTNAME= Zope-${VERSION}-src
|
||||
PKGNAME= zope-${VERSION}
|
||||
CATEGORIES= www python
|
||||
MASTER_SITES= http://www.zope.org/Products/Zope/${VERSION}/
|
||||
EXTRACT_SUFX= .tgz
|
||||
|
||||
MAINTAINER= ports@FreeBSD.ORG
|
||||
|
||||
BUILD_DEPENDS= python1.5:${PORTSDIR}/lang/python
|
||||
RUN_DEPENDS= apache:${PORTSDIR}/www/apache13-modssl
|
||||
|
||||
# Build has to be done in the final location after installing the sources
|
||||
# there. It were a major action to fix all paths otherwise.
|
||||
do-build: # empty, but needs to be there for the python dependency.
|
||||
|
||||
# The web server's "root" directory used to be ${PREFIX}/www, and from
|
||||
# then on, data, cgi-bin and such. Thus, I decided that Zope belongs
|
||||
# there, too. I don't know whether this still applies to current apache
|
||||
# releases, though. I still run 2.2.8-STABLE.
|
||||
VERSION= 2.0.0b5
|
||||
PLIST_SUB= ZOPEBASEDIR=www/Zope-${VERSION} CGIBINDIR=share/apache/cgi-bin VERSION=${VERSION}
|
||||
WEBBASEDIR?= ${PREFIX}/www
|
||||
ZOPEBASEDIR?= ${WEBBASEDIR}/Zope-${VERSION}
|
||||
CGI_BIN_DIR?= ${PREFIX}/share/apache/cgi-bin
|
||||
APACHE_CONFDIR?= ${PREFIX}/etc/apache
|
||||
PYTHON15?= ${PREFIX}/bin/python1.5
|
||||
CHMOD= /bin/chmod
|
||||
|
||||
# I decided to consider the whole souce tree to be part of the package
|
||||
# since in there, Zope can live on its own. It does leave some *.o files
|
||||
# around (about four), but I can use Zope's own building mechanism.
|
||||
do-install: #
|
||||
@if [ -e ${ZOPEBASEDIR}/var/Data.fs ] ; then \
|
||||
${ECHO} "Saving existing Database to /tmp/Data.fs.BAK." ; \
|
||||
${MV} ${ZOPEBASEDIR}/var/Data.fs /tmp/Data.fs.BAK ; \
|
||||
fi
|
||||
@( ${MKDIR} ${ZOPEBASEDIR} ; \
|
||||
${ECHO} "===> Please be patient, some builds need their time." ; \
|
||||
${ECHO} "===> Copying..." ; \
|
||||
${CP} -Rp ${WRKSRC}/* ${ZOPEBASEDIR}/ ; \
|
||||
cd ${ZOPEBASEDIR} ; \
|
||||
${PYTHON15} w_pcgi.py ; \
|
||||
${PYTHON15} wo_pcgi.py ; \
|
||||
${MV} Zope.cgi Zope.cgi.orig ; \
|
||||
${ECHO} "#! ${CGI_BIN_DIR}/pcgi-wrapper" > Zope.cgi ; \
|
||||
${CAT} Zope.cgi.orig >> Zope.cgi ; \
|
||||
${INSTALL} -o nobody -m 555 Zope.cgi pcgi/pcgi-wrapper ${CGI_BIN_DIR} ; \
|
||||
${ECHO} "===> Fixing permissions of Zope's own var directory..." ; \
|
||||
${CHMOD} ugo+rwt var ; \
|
||||
${ECHO} "===> Setting user/password to zopemaster/test..." ; \
|
||||
${PYTHON15} zpasswd.py -u zopemaster -p test -e CLEARTEXT access ; \
|
||||
${ECHO} "===> Copying Apache config file changes to ${APACHE_CONFDIR}/apache.conf.Zope-${VERSION}-Changes." ; \
|
||||
${CP} -p ${FILESDIR}/apache.conf.Zope-${VERSION}-Changes ${APACHE_CONFDIR}/ ; \
|
||||
${ECHO} "===> Please have a look at this file and the instructions" ; \
|
||||
${ECHO} "===> therein and incorporate them to your apache.conf." ; \
|
||||
${ECHO} "===> Creating rc startup file for Zope-${VERSION}..." ; \
|
||||
${ECHO} "#! /bin/sh" > ${PREFIX}/etc/rc.d/zope.sh ; \
|
||||
${ECHO} "${ZOPEBASEDIR}/start -w '' -f '' -m '' -p ${CGI_BIN_DIR}/Zope.cgi &" >> ${PREFIX}/etc/rc.d/zope.sh ; \
|
||||
${ECHO} "echo -n \" Zope\"" >> ${PREFIX}/etc/rc.d/zope.sh ; \
|
||||
${CHMOD} ug+x,o-rwx ${PREFIX}/etc/rc.d/zope.sh ; \
|
||||
${ECHO} "===> Done with ${PREFIX}/etc/rc.d/zope.sh." ; \
|
||||
${CAT} ${FILESDIR}/Message ; \
|
||||
${ECHO} "===> Your Zope base directory is ${ZOPEBASEDIR}." ; \
|
||||
${ECHO} "===> The Zope license is in ${ZOPEBASEDIR}/LICENSE.txt." ; \
|
||||
${ECHO} "===> For Apache changes see ${APACHE_CONFDIR}/apache.conf.Zope-${VERSION}-Changes." ; \
|
||||
${ECHO} "===> Zope.cgi and pcgi-wrapper live in ${CGI_BIN_DIR}." )
|
||||
|
||||
#pre-deinstall: # Save Database contents. I expect /tmp to have sufficient
|
||||
# # space to hold it for the time being.
|
||||
# @if [ -e ${ZOPEBASEDIR}/var/Data.fs ] ; then \
|
||||
# ${ECHO} "Saving existing Database to /tmp/Data.fs.bak." ; \
|
||||
# ${MV} ${ZOPEBASEDIR}/var/Data.fs /tmp/Data.fs.bak ; \
|
||||
# fi
|
||||
|
||||
.include <bsd.port.mk>
|
||||
1
www/zope/distinfo
Normal file
1
www/zope/distinfo
Normal file
|
|
@ -0,0 +1 @@
|
|||
MD5 (Zope-2.0.0b5-src.tgz) = 22916a3b0852ee5eba3c2b42e160bc31
|
||||
6
www/zope/files/CREDITS
Normal file
6
www/zope/files/CREDITS
Normal file
|
|
@ -0,0 +1,6 @@
|
|||
Special thanks to (in no particular order):
|
||||
|
||||
- The Zope makers: Digital Creations.
|
||||
- The Python Group
|
||||
- Olaf Erb
|
||||
- Andreas Ley
|
||||
57
www/zope/files/Message
Normal file
57
www/zope/files/Message
Normal file
|
|
@ -0,0 +1,57 @@
|
|||
|
||||
Welcome to Zope.
|
||||
|
||||
The basic installation process for FreeBSD now has been done. To have a
|
||||
quick look, cd to your Zope base directory (see below) and start Zope
|
||||
with:
|
||||
|
||||
./start -w <web port> -f <ftp port>
|
||||
|
||||
where <web port> is the port where to http-access Zope with your browser
|
||||
(try http://localhost:<web port>). It defaults to 80. <ftp-port> is the
|
||||
same thing for ftp (upload) access, it defaults to 21. Obviously, you will
|
||||
have to specify these if you already use these ports. The user/password
|
||||
pair for access to the management screens has been preset to
|
||||
zopemaster/test, respectively.
|
||||
|
||||
PLEASE NOTE that the above only is for a quick check only, BUT IT WILL
|
||||
LEAVE YOUR ZOPE PROCESS WIDE OPEN TO HACKING SINCE THERE'S NO SECURITY
|
||||
WHATSOEVER. Therefore, PLEASE do incorporate the suggested changes (see
|
||||
below) to your apache-SSL web server and only start Zope WITHOUT ANY open
|
||||
<web port> or <ftp port>. This can be done, also from the Zope base dir,
|
||||
by:
|
||||
|
||||
./start -w '' -f '' -m '' -p <path to Zope.cgi>/Zope.cgi
|
||||
|
||||
where <path to Zope.cgi> is the (full) path to where Zope.cgi lives (see
|
||||
below). There now also should be a file in ${PREFIX}/etc/rc.d/ (most
|
||||
probably /usr/local/etc/rc.d/) named zope.sh that does the startup for you
|
||||
after a reboot.
|
||||
|
||||
Also, it might be a good idea now to change the password. You can do that
|
||||
with (again, in the Zope base directory):
|
||||
|
||||
python zpasswd.py -u <username> -p <passwd> -e CLEARTEXT access
|
||||
|
||||
The -e CLEARTEXT presently is *mandatory*, otherwise authentication
|
||||
through apache will not work.
|
||||
|
||||
You will probably already have gone through Apache's ssl certificate
|
||||
generation process. If not, please do so now, if you don't already have a
|
||||
certificate. If only a few well known people will have access to your
|
||||
management screens, a self-signed one probably will suffice. Please refer
|
||||
to the Apache and the Apache-SSL documentation for further information.
|
||||
Use a sufficiently "long" key. Don't forget the https://... when trying to
|
||||
access the management pages.
|
||||
|
||||
Apache will communicate with Zope through the so-called persistent cgi
|
||||
interface (aka pcgi). There's links to more information on the Zope web
|
||||
site at http://www.zope.org. Also, this is the best (and only) source of
|
||||
help end information on Zope itself.
|
||||
|
||||
Zope is Copyrighted (C) by Digital Creations. All rights reserved.
|
||||
Please thouroughly read the license (see below) before employing Zope.
|
||||
|
||||
Good business, Peter Cornelius. <pcc@gmx.net>
|
||||
|
||||
Please remember these files and directories:
|
||||
1
www/zope/pkg-comment
Normal file
1
www/zope/pkg-comment
Normal file
|
|
@ -0,0 +1 @@
|
|||
An object-based web application platform with database access
|
||||
25
www/zope/pkg-descr
Normal file
25
www/zope/pkg-descr
Normal file
|
|
@ -0,0 +1,25 @@
|
|||
Zope is Copyrighted (C) Digital Creations. All rights reserved. This is
|
||||
what they themselves say about it:
|
||||
|
||||
"Zope (WWW: http://www.zope.org/ ) is an exciting new object-based, open
|
||||
source web application platform. It allows you to build powerful and
|
||||
dynamic web applications easily. Zope comes with source code and is
|
||||
friendly to developers as well as users.
|
||||
Zope is distinguished by its integrated object database which, when
|
||||
combined with a revolutionary object model, provides a completely unique
|
||||
facility for servicing content managers and web application developers."
|
||||
|
||||
Here are some of the "headlines" mentioned in the features list at
|
||||
WWW: http://www.zope.org/Information/Features :
|
||||
|
||||
Database Integration Content Management
|
||||
SQL and HTML in Harmony Builtin Objects
|
||||
Multiple Data Sources Document Templates
|
||||
Publish Databases Web to Objects
|
||||
Application Development Integrated Object Database
|
||||
DTML Scripting Managed Through the Web
|
||||
External Methods Direct URL Access to Objects
|
||||
|
||||
This is a "beta" release. It seems to work quite stable, but no guarantee
|
||||
given.
|
||||
Peter Cornelius <pcc@gmx.net>
|
||||
1108
www/zope/pkg-plist
Normal file
1108
www/zope/pkg-plist
Normal file
File diff suppressed because it is too large
Load diff
82
www/zope210/Makefile
Normal file
82
www/zope210/Makefile
Normal file
|
|
@ -0,0 +1,82 @@
|
|||
# New ports collection makefile for: Zope
|
||||
# Version required: 2.0.1
|
||||
# Date created: Sat 21 Aug 1999
|
||||
# Whom: Peter Cornelius <pcc@gmx.net>
|
||||
#
|
||||
# $FreeBSD$
|
||||
|
||||
DISTNAME= Zope-${VERSION}-src
|
||||
PKGNAME= zope-${VERSION}
|
||||
CATEGORIES= www python
|
||||
MASTER_SITES= http://www.zope.org/Products/Zope/${VERSION}/
|
||||
EXTRACT_SUFX= .tgz
|
||||
|
||||
MAINTAINER= ports@FreeBSD.ORG
|
||||
|
||||
BUILD_DEPENDS= python1.5:${PORTSDIR}/lang/python
|
||||
RUN_DEPENDS= apache:${PORTSDIR}/www/apache13-modssl
|
||||
|
||||
# Build has to be done in the final location after installing the sources
|
||||
# there. It were a major action to fix all paths otherwise.
|
||||
do-build: # empty, but needs to be there for the python dependency.
|
||||
|
||||
# The web server's "root" directory used to be ${PREFIX}/www, and from
|
||||
# then on, data, cgi-bin and such. Thus, I decided that Zope belongs
|
||||
# there, too. I don't know whether this still applies to current apache
|
||||
# releases, though. I still run 2.2.8-STABLE.
|
||||
VERSION= 2.0.0b5
|
||||
PLIST_SUB= ZOPEBASEDIR=www/Zope-${VERSION} CGIBINDIR=share/apache/cgi-bin VERSION=${VERSION}
|
||||
WEBBASEDIR?= ${PREFIX}/www
|
||||
ZOPEBASEDIR?= ${WEBBASEDIR}/Zope-${VERSION}
|
||||
CGI_BIN_DIR?= ${PREFIX}/share/apache/cgi-bin
|
||||
APACHE_CONFDIR?= ${PREFIX}/etc/apache
|
||||
PYTHON15?= ${PREFIX}/bin/python1.5
|
||||
CHMOD= /bin/chmod
|
||||
|
||||
# I decided to consider the whole souce tree to be part of the package
|
||||
# since in there, Zope can live on its own. It does leave some *.o files
|
||||
# around (about four), but I can use Zope's own building mechanism.
|
||||
do-install: #
|
||||
@if [ -e ${ZOPEBASEDIR}/var/Data.fs ] ; then \
|
||||
${ECHO} "Saving existing Database to /tmp/Data.fs.BAK." ; \
|
||||
${MV} ${ZOPEBASEDIR}/var/Data.fs /tmp/Data.fs.BAK ; \
|
||||
fi
|
||||
@( ${MKDIR} ${ZOPEBASEDIR} ; \
|
||||
${ECHO} "===> Please be patient, some builds need their time." ; \
|
||||
${ECHO} "===> Copying..." ; \
|
||||
${CP} -Rp ${WRKSRC}/* ${ZOPEBASEDIR}/ ; \
|
||||
cd ${ZOPEBASEDIR} ; \
|
||||
${PYTHON15} w_pcgi.py ; \
|
||||
${PYTHON15} wo_pcgi.py ; \
|
||||
${MV} Zope.cgi Zope.cgi.orig ; \
|
||||
${ECHO} "#! ${CGI_BIN_DIR}/pcgi-wrapper" > Zope.cgi ; \
|
||||
${CAT} Zope.cgi.orig >> Zope.cgi ; \
|
||||
${INSTALL} -o nobody -m 555 Zope.cgi pcgi/pcgi-wrapper ${CGI_BIN_DIR} ; \
|
||||
${ECHO} "===> Fixing permissions of Zope's own var directory..." ; \
|
||||
${CHMOD} ugo+rwt var ; \
|
||||
${ECHO} "===> Setting user/password to zopemaster/test..." ; \
|
||||
${PYTHON15} zpasswd.py -u zopemaster -p test -e CLEARTEXT access ; \
|
||||
${ECHO} "===> Copying Apache config file changes to ${APACHE_CONFDIR}/apache.conf.Zope-${VERSION}-Changes." ; \
|
||||
${CP} -p ${FILESDIR}/apache.conf.Zope-${VERSION}-Changes ${APACHE_CONFDIR}/ ; \
|
||||
${ECHO} "===> Please have a look at this file and the instructions" ; \
|
||||
${ECHO} "===> therein and incorporate them to your apache.conf." ; \
|
||||
${ECHO} "===> Creating rc startup file for Zope-${VERSION}..." ; \
|
||||
${ECHO} "#! /bin/sh" > ${PREFIX}/etc/rc.d/zope.sh ; \
|
||||
${ECHO} "${ZOPEBASEDIR}/start -w '' -f '' -m '' -p ${CGI_BIN_DIR}/Zope.cgi &" >> ${PREFIX}/etc/rc.d/zope.sh ; \
|
||||
${ECHO} "echo -n \" Zope\"" >> ${PREFIX}/etc/rc.d/zope.sh ; \
|
||||
${CHMOD} ug+x,o-rwx ${PREFIX}/etc/rc.d/zope.sh ; \
|
||||
${ECHO} "===> Done with ${PREFIX}/etc/rc.d/zope.sh." ; \
|
||||
${CAT} ${FILESDIR}/Message ; \
|
||||
${ECHO} "===> Your Zope base directory is ${ZOPEBASEDIR}." ; \
|
||||
${ECHO} "===> The Zope license is in ${ZOPEBASEDIR}/LICENSE.txt." ; \
|
||||
${ECHO} "===> For Apache changes see ${APACHE_CONFDIR}/apache.conf.Zope-${VERSION}-Changes." ; \
|
||||
${ECHO} "===> Zope.cgi and pcgi-wrapper live in ${CGI_BIN_DIR}." )
|
||||
|
||||
#pre-deinstall: # Save Database contents. I expect /tmp to have sufficient
|
||||
# # space to hold it for the time being.
|
||||
# @if [ -e ${ZOPEBASEDIR}/var/Data.fs ] ; then \
|
||||
# ${ECHO} "Saving existing Database to /tmp/Data.fs.bak." ; \
|
||||
# ${MV} ${ZOPEBASEDIR}/var/Data.fs /tmp/Data.fs.bak ; \
|
||||
# fi
|
||||
|
||||
.include <bsd.port.mk>
|
||||
1
www/zope210/distinfo
Normal file
1
www/zope210/distinfo
Normal file
|
|
@ -0,0 +1 @@
|
|||
MD5 (Zope-2.0.0b5-src.tgz) = 22916a3b0852ee5eba3c2b42e160bc31
|
||||
6
www/zope210/files/CREDITS
Normal file
6
www/zope210/files/CREDITS
Normal file
|
|
@ -0,0 +1,6 @@
|
|||
Special thanks to (in no particular order):
|
||||
|
||||
- The Zope makers: Digital Creations.
|
||||
- The Python Group
|
||||
- Olaf Erb
|
||||
- Andreas Ley
|
||||
57
www/zope210/files/Message
Normal file
57
www/zope210/files/Message
Normal file
|
|
@ -0,0 +1,57 @@
|
|||
|
||||
Welcome to Zope.
|
||||
|
||||
The basic installation process for FreeBSD now has been done. To have a
|
||||
quick look, cd to your Zope base directory (see below) and start Zope
|
||||
with:
|
||||
|
||||
./start -w <web port> -f <ftp port>
|
||||
|
||||
where <web port> is the port where to http-access Zope with your browser
|
||||
(try http://localhost:<web port>). It defaults to 80. <ftp-port> is the
|
||||
same thing for ftp (upload) access, it defaults to 21. Obviously, you will
|
||||
have to specify these if you already use these ports. The user/password
|
||||
pair for access to the management screens has been preset to
|
||||
zopemaster/test, respectively.
|
||||
|
||||
PLEASE NOTE that the above only is for a quick check only, BUT IT WILL
|
||||
LEAVE YOUR ZOPE PROCESS WIDE OPEN TO HACKING SINCE THERE'S NO SECURITY
|
||||
WHATSOEVER. Therefore, PLEASE do incorporate the suggested changes (see
|
||||
below) to your apache-SSL web server and only start Zope WITHOUT ANY open
|
||||
<web port> or <ftp port>. This can be done, also from the Zope base dir,
|
||||
by:
|
||||
|
||||
./start -w '' -f '' -m '' -p <path to Zope.cgi>/Zope.cgi
|
||||
|
||||
where <path to Zope.cgi> is the (full) path to where Zope.cgi lives (see
|
||||
below). There now also should be a file in ${PREFIX}/etc/rc.d/ (most
|
||||
probably /usr/local/etc/rc.d/) named zope.sh that does the startup for you
|
||||
after a reboot.
|
||||
|
||||
Also, it might be a good idea now to change the password. You can do that
|
||||
with (again, in the Zope base directory):
|
||||
|
||||
python zpasswd.py -u <username> -p <passwd> -e CLEARTEXT access
|
||||
|
||||
The -e CLEARTEXT presently is *mandatory*, otherwise authentication
|
||||
through apache will not work.
|
||||
|
||||
You will probably already have gone through Apache's ssl certificate
|
||||
generation process. If not, please do so now, if you don't already have a
|
||||
certificate. If only a few well known people will have access to your
|
||||
management screens, a self-signed one probably will suffice. Please refer
|
||||
to the Apache and the Apache-SSL documentation for further information.
|
||||
Use a sufficiently "long" key. Don't forget the https://... when trying to
|
||||
access the management pages.
|
||||
|
||||
Apache will communicate with Zope through the so-called persistent cgi
|
||||
interface (aka pcgi). There's links to more information on the Zope web
|
||||
site at http://www.zope.org. Also, this is the best (and only) source of
|
||||
help end information on Zope itself.
|
||||
|
||||
Zope is Copyrighted (C) by Digital Creations. All rights reserved.
|
||||
Please thouroughly read the license (see below) before employing Zope.
|
||||
|
||||
Good business, Peter Cornelius. <pcc@gmx.net>
|
||||
|
||||
Please remember these files and directories:
|
||||
1
www/zope210/pkg-comment
Normal file
1
www/zope210/pkg-comment
Normal file
|
|
@ -0,0 +1 @@
|
|||
An object-based web application platform with database access
|
||||
25
www/zope210/pkg-descr
Normal file
25
www/zope210/pkg-descr
Normal file
|
|
@ -0,0 +1,25 @@
|
|||
Zope is Copyrighted (C) Digital Creations. All rights reserved. This is
|
||||
what they themselves say about it:
|
||||
|
||||
"Zope (WWW: http://www.zope.org/ ) is an exciting new object-based, open
|
||||
source web application platform. It allows you to build powerful and
|
||||
dynamic web applications easily. Zope comes with source code and is
|
||||
friendly to developers as well as users.
|
||||
Zope is distinguished by its integrated object database which, when
|
||||
combined with a revolutionary object model, provides a completely unique
|
||||
facility for servicing content managers and web application developers."
|
||||
|
||||
Here are some of the "headlines" mentioned in the features list at
|
||||
WWW: http://www.zope.org/Information/Features :
|
||||
|
||||
Database Integration Content Management
|
||||
SQL and HTML in Harmony Builtin Objects
|
||||
Multiple Data Sources Document Templates
|
||||
Publish Databases Web to Objects
|
||||
Application Development Integrated Object Database
|
||||
DTML Scripting Managed Through the Web
|
||||
External Methods Direct URL Access to Objects
|
||||
|
||||
This is a "beta" release. It seems to work quite stable, but no guarantee
|
||||
given.
|
||||
Peter Cornelius <pcc@gmx.net>
|
||||
1108
www/zope210/pkg-plist
Normal file
1108
www/zope210/pkg-plist
Normal file
File diff suppressed because it is too large
Load diff
82
www/zope211/Makefile
Normal file
82
www/zope211/Makefile
Normal file
|
|
@ -0,0 +1,82 @@
|
|||
# New ports collection makefile for: Zope
|
||||
# Version required: 2.0.1
|
||||
# Date created: Sat 21 Aug 1999
|
||||
# Whom: Peter Cornelius <pcc@gmx.net>
|
||||
#
|
||||
# $FreeBSD$
|
||||
|
||||
DISTNAME= Zope-${VERSION}-src
|
||||
PKGNAME= zope-${VERSION}
|
||||
CATEGORIES= www python
|
||||
MASTER_SITES= http://www.zope.org/Products/Zope/${VERSION}/
|
||||
EXTRACT_SUFX= .tgz
|
||||
|
||||
MAINTAINER= ports@FreeBSD.ORG
|
||||
|
||||
BUILD_DEPENDS= python1.5:${PORTSDIR}/lang/python
|
||||
RUN_DEPENDS= apache:${PORTSDIR}/www/apache13-modssl
|
||||
|
||||
# Build has to be done in the final location after installing the sources
|
||||
# there. It were a major action to fix all paths otherwise.
|
||||
do-build: # empty, but needs to be there for the python dependency.
|
||||
|
||||
# The web server's "root" directory used to be ${PREFIX}/www, and from
|
||||
# then on, data, cgi-bin and such. Thus, I decided that Zope belongs
|
||||
# there, too. I don't know whether this still applies to current apache
|
||||
# releases, though. I still run 2.2.8-STABLE.
|
||||
VERSION= 2.0.0b5
|
||||
PLIST_SUB= ZOPEBASEDIR=www/Zope-${VERSION} CGIBINDIR=share/apache/cgi-bin VERSION=${VERSION}
|
||||
WEBBASEDIR?= ${PREFIX}/www
|
||||
ZOPEBASEDIR?= ${WEBBASEDIR}/Zope-${VERSION}
|
||||
CGI_BIN_DIR?= ${PREFIX}/share/apache/cgi-bin
|
||||
APACHE_CONFDIR?= ${PREFIX}/etc/apache
|
||||
PYTHON15?= ${PREFIX}/bin/python1.5
|
||||
CHMOD= /bin/chmod
|
||||
|
||||
# I decided to consider the whole souce tree to be part of the package
|
||||
# since in there, Zope can live on its own. It does leave some *.o files
|
||||
# around (about four), but I can use Zope's own building mechanism.
|
||||
do-install: #
|
||||
@if [ -e ${ZOPEBASEDIR}/var/Data.fs ] ; then \
|
||||
${ECHO} "Saving existing Database to /tmp/Data.fs.BAK." ; \
|
||||
${MV} ${ZOPEBASEDIR}/var/Data.fs /tmp/Data.fs.BAK ; \
|
||||
fi
|
||||
@( ${MKDIR} ${ZOPEBASEDIR} ; \
|
||||
${ECHO} "===> Please be patient, some builds need their time." ; \
|
||||
${ECHO} "===> Copying..." ; \
|
||||
${CP} -Rp ${WRKSRC}/* ${ZOPEBASEDIR}/ ; \
|
||||
cd ${ZOPEBASEDIR} ; \
|
||||
${PYTHON15} w_pcgi.py ; \
|
||||
${PYTHON15} wo_pcgi.py ; \
|
||||
${MV} Zope.cgi Zope.cgi.orig ; \
|
||||
${ECHO} "#! ${CGI_BIN_DIR}/pcgi-wrapper" > Zope.cgi ; \
|
||||
${CAT} Zope.cgi.orig >> Zope.cgi ; \
|
||||
${INSTALL} -o nobody -m 555 Zope.cgi pcgi/pcgi-wrapper ${CGI_BIN_DIR} ; \
|
||||
${ECHO} "===> Fixing permissions of Zope's own var directory..." ; \
|
||||
${CHMOD} ugo+rwt var ; \
|
||||
${ECHO} "===> Setting user/password to zopemaster/test..." ; \
|
||||
${PYTHON15} zpasswd.py -u zopemaster -p test -e CLEARTEXT access ; \
|
||||
${ECHO} "===> Copying Apache config file changes to ${APACHE_CONFDIR}/apache.conf.Zope-${VERSION}-Changes." ; \
|
||||
${CP} -p ${FILESDIR}/apache.conf.Zope-${VERSION}-Changes ${APACHE_CONFDIR}/ ; \
|
||||
${ECHO} "===> Please have a look at this file and the instructions" ; \
|
||||
${ECHO} "===> therein and incorporate them to your apache.conf." ; \
|
||||
${ECHO} "===> Creating rc startup file for Zope-${VERSION}..." ; \
|
||||
${ECHO} "#! /bin/sh" > ${PREFIX}/etc/rc.d/zope.sh ; \
|
||||
${ECHO} "${ZOPEBASEDIR}/start -w '' -f '' -m '' -p ${CGI_BIN_DIR}/Zope.cgi &" >> ${PREFIX}/etc/rc.d/zope.sh ; \
|
||||
${ECHO} "echo -n \" Zope\"" >> ${PREFIX}/etc/rc.d/zope.sh ; \
|
||||
${CHMOD} ug+x,o-rwx ${PREFIX}/etc/rc.d/zope.sh ; \
|
||||
${ECHO} "===> Done with ${PREFIX}/etc/rc.d/zope.sh." ; \
|
||||
${CAT} ${FILESDIR}/Message ; \
|
||||
${ECHO} "===> Your Zope base directory is ${ZOPEBASEDIR}." ; \
|
||||
${ECHO} "===> The Zope license is in ${ZOPEBASEDIR}/LICENSE.txt." ; \
|
||||
${ECHO} "===> For Apache changes see ${APACHE_CONFDIR}/apache.conf.Zope-${VERSION}-Changes." ; \
|
||||
${ECHO} "===> Zope.cgi and pcgi-wrapper live in ${CGI_BIN_DIR}." )
|
||||
|
||||
#pre-deinstall: # Save Database contents. I expect /tmp to have sufficient
|
||||
# # space to hold it for the time being.
|
||||
# @if [ -e ${ZOPEBASEDIR}/var/Data.fs ] ; then \
|
||||
# ${ECHO} "Saving existing Database to /tmp/Data.fs.bak." ; \
|
||||
# ${MV} ${ZOPEBASEDIR}/var/Data.fs /tmp/Data.fs.bak ; \
|
||||
# fi
|
||||
|
||||
.include <bsd.port.mk>
|
||||
1
www/zope211/distinfo
Normal file
1
www/zope211/distinfo
Normal file
|
|
@ -0,0 +1 @@
|
|||
MD5 (Zope-2.0.0b5-src.tgz) = 22916a3b0852ee5eba3c2b42e160bc31
|
||||
6
www/zope211/files/CREDITS
Normal file
6
www/zope211/files/CREDITS
Normal file
|
|
@ -0,0 +1,6 @@
|
|||
Special thanks to (in no particular order):
|
||||
|
||||
- The Zope makers: Digital Creations.
|
||||
- The Python Group
|
||||
- Olaf Erb
|
||||
- Andreas Ley
|
||||
57
www/zope211/files/Message
Normal file
57
www/zope211/files/Message
Normal file
|
|
@ -0,0 +1,57 @@
|
|||
|
||||
Welcome to Zope.
|
||||
|
||||
The basic installation process for FreeBSD now has been done. To have a
|
||||
quick look, cd to your Zope base directory (see below) and start Zope
|
||||
with:
|
||||
|
||||
./start -w <web port> -f <ftp port>
|
||||
|
||||
where <web port> is the port where to http-access Zope with your browser
|
||||
(try http://localhost:<web port>). It defaults to 80. <ftp-port> is the
|
||||
same thing for ftp (upload) access, it defaults to 21. Obviously, you will
|
||||
have to specify these if you already use these ports. The user/password
|
||||
pair for access to the management screens has been preset to
|
||||
zopemaster/test, respectively.
|
||||
|
||||
PLEASE NOTE that the above only is for a quick check only, BUT IT WILL
|
||||
LEAVE YOUR ZOPE PROCESS WIDE OPEN TO HACKING SINCE THERE'S NO SECURITY
|
||||
WHATSOEVER. Therefore, PLEASE do incorporate the suggested changes (see
|
||||
below) to your apache-SSL web server and only start Zope WITHOUT ANY open
|
||||
<web port> or <ftp port>. This can be done, also from the Zope base dir,
|
||||
by:
|
||||
|
||||
./start -w '' -f '' -m '' -p <path to Zope.cgi>/Zope.cgi
|
||||
|
||||
where <path to Zope.cgi> is the (full) path to where Zope.cgi lives (see
|
||||
below). There now also should be a file in ${PREFIX}/etc/rc.d/ (most
|
||||
probably /usr/local/etc/rc.d/) named zope.sh that does the startup for you
|
||||
after a reboot.
|
||||
|
||||
Also, it might be a good idea now to change the password. You can do that
|
||||
with (again, in the Zope base directory):
|
||||
|
||||
python zpasswd.py -u <username> -p <passwd> -e CLEARTEXT access
|
||||
|
||||
The -e CLEARTEXT presently is *mandatory*, otherwise authentication
|
||||
through apache will not work.
|
||||
|
||||
You will probably already have gone through Apache's ssl certificate
|
||||
generation process. If not, please do so now, if you don't already have a
|
||||
certificate. If only a few well known people will have access to your
|
||||
management screens, a self-signed one probably will suffice. Please refer
|
||||
to the Apache and the Apache-SSL documentation for further information.
|
||||
Use a sufficiently "long" key. Don't forget the https://... when trying to
|
||||
access the management pages.
|
||||
|
||||
Apache will communicate with Zope through the so-called persistent cgi
|
||||
interface (aka pcgi). There's links to more information on the Zope web
|
||||
site at http://www.zope.org. Also, this is the best (and only) source of
|
||||
help end information on Zope itself.
|
||||
|
||||
Zope is Copyrighted (C) by Digital Creations. All rights reserved.
|
||||
Please thouroughly read the license (see below) before employing Zope.
|
||||
|
||||
Good business, Peter Cornelius. <pcc@gmx.net>
|
||||
|
||||
Please remember these files and directories:
|
||||
1
www/zope211/pkg-comment
Normal file
1
www/zope211/pkg-comment
Normal file
|
|
@ -0,0 +1 @@
|
|||
An object-based web application platform with database access
|
||||
25
www/zope211/pkg-descr
Normal file
25
www/zope211/pkg-descr
Normal file
|
|
@ -0,0 +1,25 @@
|
|||
Zope is Copyrighted (C) Digital Creations. All rights reserved. This is
|
||||
what they themselves say about it:
|
||||
|
||||
"Zope (WWW: http://www.zope.org/ ) is an exciting new object-based, open
|
||||
source web application platform. It allows you to build powerful and
|
||||
dynamic web applications easily. Zope comes with source code and is
|
||||
friendly to developers as well as users.
|
||||
Zope is distinguished by its integrated object database which, when
|
||||
combined with a revolutionary object model, provides a completely unique
|
||||
facility for servicing content managers and web application developers."
|
||||
|
||||
Here are some of the "headlines" mentioned in the features list at
|
||||
WWW: http://www.zope.org/Information/Features :
|
||||
|
||||
Database Integration Content Management
|
||||
SQL and HTML in Harmony Builtin Objects
|
||||
Multiple Data Sources Document Templates
|
||||
Publish Databases Web to Objects
|
||||
Application Development Integrated Object Database
|
||||
DTML Scripting Managed Through the Web
|
||||
External Methods Direct URL Access to Objects
|
||||
|
||||
This is a "beta" release. It seems to work quite stable, but no guarantee
|
||||
given.
|
||||
Peter Cornelius <pcc@gmx.net>
|
||||
1108
www/zope211/pkg-plist
Normal file
1108
www/zope211/pkg-plist
Normal file
File diff suppressed because it is too large
Load diff
82
www/zope213/Makefile
Normal file
82
www/zope213/Makefile
Normal file
|
|
@ -0,0 +1,82 @@
|
|||
# New ports collection makefile for: Zope
|
||||
# Version required: 2.0.1
|
||||
# Date created: Sat 21 Aug 1999
|
||||
# Whom: Peter Cornelius <pcc@gmx.net>
|
||||
#
|
||||
# $FreeBSD$
|
||||
|
||||
DISTNAME= Zope-${VERSION}-src
|
||||
PKGNAME= zope-${VERSION}
|
||||
CATEGORIES= www python
|
||||
MASTER_SITES= http://www.zope.org/Products/Zope/${VERSION}/
|
||||
EXTRACT_SUFX= .tgz
|
||||
|
||||
MAINTAINER= ports@FreeBSD.ORG
|
||||
|
||||
BUILD_DEPENDS= python1.5:${PORTSDIR}/lang/python
|
||||
RUN_DEPENDS= apache:${PORTSDIR}/www/apache13-modssl
|
||||
|
||||
# Build has to be done in the final location after installing the sources
|
||||
# there. It were a major action to fix all paths otherwise.
|
||||
do-build: # empty, but needs to be there for the python dependency.
|
||||
|
||||
# The web server's "root" directory used to be ${PREFIX}/www, and from
|
||||
# then on, data, cgi-bin and such. Thus, I decided that Zope belongs
|
||||
# there, too. I don't know whether this still applies to current apache
|
||||
# releases, though. I still run 2.2.8-STABLE.
|
||||
VERSION= 2.0.0b5
|
||||
PLIST_SUB= ZOPEBASEDIR=www/Zope-${VERSION} CGIBINDIR=share/apache/cgi-bin VERSION=${VERSION}
|
||||
WEBBASEDIR?= ${PREFIX}/www
|
||||
ZOPEBASEDIR?= ${WEBBASEDIR}/Zope-${VERSION}
|
||||
CGI_BIN_DIR?= ${PREFIX}/share/apache/cgi-bin
|
||||
APACHE_CONFDIR?= ${PREFIX}/etc/apache
|
||||
PYTHON15?= ${PREFIX}/bin/python1.5
|
||||
CHMOD= /bin/chmod
|
||||
|
||||
# I decided to consider the whole souce tree to be part of the package
|
||||
# since in there, Zope can live on its own. It does leave some *.o files
|
||||
# around (about four), but I can use Zope's own building mechanism.
|
||||
do-install: #
|
||||
@if [ -e ${ZOPEBASEDIR}/var/Data.fs ] ; then \
|
||||
${ECHO} "Saving existing Database to /tmp/Data.fs.BAK." ; \
|
||||
${MV} ${ZOPEBASEDIR}/var/Data.fs /tmp/Data.fs.BAK ; \
|
||||
fi
|
||||
@( ${MKDIR} ${ZOPEBASEDIR} ; \
|
||||
${ECHO} "===> Please be patient, some builds need their time." ; \
|
||||
${ECHO} "===> Copying..." ; \
|
||||
${CP} -Rp ${WRKSRC}/* ${ZOPEBASEDIR}/ ; \
|
||||
cd ${ZOPEBASEDIR} ; \
|
||||
${PYTHON15} w_pcgi.py ; \
|
||||
${PYTHON15} wo_pcgi.py ; \
|
||||
${MV} Zope.cgi Zope.cgi.orig ; \
|
||||
${ECHO} "#! ${CGI_BIN_DIR}/pcgi-wrapper" > Zope.cgi ; \
|
||||
${CAT} Zope.cgi.orig >> Zope.cgi ; \
|
||||
${INSTALL} -o nobody -m 555 Zope.cgi pcgi/pcgi-wrapper ${CGI_BIN_DIR} ; \
|
||||
${ECHO} "===> Fixing permissions of Zope's own var directory..." ; \
|
||||
${CHMOD} ugo+rwt var ; \
|
||||
${ECHO} "===> Setting user/password to zopemaster/test..." ; \
|
||||
${PYTHON15} zpasswd.py -u zopemaster -p test -e CLEARTEXT access ; \
|
||||
${ECHO} "===> Copying Apache config file changes to ${APACHE_CONFDIR}/apache.conf.Zope-${VERSION}-Changes." ; \
|
||||
${CP} -p ${FILESDIR}/apache.conf.Zope-${VERSION}-Changes ${APACHE_CONFDIR}/ ; \
|
||||
${ECHO} "===> Please have a look at this file and the instructions" ; \
|
||||
${ECHO} "===> therein and incorporate them to your apache.conf." ; \
|
||||
${ECHO} "===> Creating rc startup file for Zope-${VERSION}..." ; \
|
||||
${ECHO} "#! /bin/sh" > ${PREFIX}/etc/rc.d/zope.sh ; \
|
||||
${ECHO} "${ZOPEBASEDIR}/start -w '' -f '' -m '' -p ${CGI_BIN_DIR}/Zope.cgi &" >> ${PREFIX}/etc/rc.d/zope.sh ; \
|
||||
${ECHO} "echo -n \" Zope\"" >> ${PREFIX}/etc/rc.d/zope.sh ; \
|
||||
${CHMOD} ug+x,o-rwx ${PREFIX}/etc/rc.d/zope.sh ; \
|
||||
${ECHO} "===> Done with ${PREFIX}/etc/rc.d/zope.sh." ; \
|
||||
${CAT} ${FILESDIR}/Message ; \
|
||||
${ECHO} "===> Your Zope base directory is ${ZOPEBASEDIR}." ; \
|
||||
${ECHO} "===> The Zope license is in ${ZOPEBASEDIR}/LICENSE.txt." ; \
|
||||
${ECHO} "===> For Apache changes see ${APACHE_CONFDIR}/apache.conf.Zope-${VERSION}-Changes." ; \
|
||||
${ECHO} "===> Zope.cgi and pcgi-wrapper live in ${CGI_BIN_DIR}." )
|
||||
|
||||
#pre-deinstall: # Save Database contents. I expect /tmp to have sufficient
|
||||
# # space to hold it for the time being.
|
||||
# @if [ -e ${ZOPEBASEDIR}/var/Data.fs ] ; then \
|
||||
# ${ECHO} "Saving existing Database to /tmp/Data.fs.bak." ; \
|
||||
# ${MV} ${ZOPEBASEDIR}/var/Data.fs /tmp/Data.fs.bak ; \
|
||||
# fi
|
||||
|
||||
.include <bsd.port.mk>
|
||||
1
www/zope213/distinfo
Normal file
1
www/zope213/distinfo
Normal file
|
|
@ -0,0 +1 @@
|
|||
MD5 (Zope-2.0.0b5-src.tgz) = 22916a3b0852ee5eba3c2b42e160bc31
|
||||
6
www/zope213/files/CREDITS
Normal file
6
www/zope213/files/CREDITS
Normal file
|
|
@ -0,0 +1,6 @@
|
|||
Special thanks to (in no particular order):
|
||||
|
||||
- The Zope makers: Digital Creations.
|
||||
- The Python Group
|
||||
- Olaf Erb
|
||||
- Andreas Ley
|
||||
57
www/zope213/files/Message
Normal file
57
www/zope213/files/Message
Normal file
|
|
@ -0,0 +1,57 @@
|
|||
|
||||
Welcome to Zope.
|
||||
|
||||
The basic installation process for FreeBSD now has been done. To have a
|
||||
quick look, cd to your Zope base directory (see below) and start Zope
|
||||
with:
|
||||
|
||||
./start -w <web port> -f <ftp port>
|
||||
|
||||
where <web port> is the port where to http-access Zope with your browser
|
||||
(try http://localhost:<web port>). It defaults to 80. <ftp-port> is the
|
||||
same thing for ftp (upload) access, it defaults to 21. Obviously, you will
|
||||
have to specify these if you already use these ports. The user/password
|
||||
pair for access to the management screens has been preset to
|
||||
zopemaster/test, respectively.
|
||||
|
||||
PLEASE NOTE that the above only is for a quick check only, BUT IT WILL
|
||||
LEAVE YOUR ZOPE PROCESS WIDE OPEN TO HACKING SINCE THERE'S NO SECURITY
|
||||
WHATSOEVER. Therefore, PLEASE do incorporate the suggested changes (see
|
||||
below) to your apache-SSL web server and only start Zope WITHOUT ANY open
|
||||
<web port> or <ftp port>. This can be done, also from the Zope base dir,
|
||||
by:
|
||||
|
||||
./start -w '' -f '' -m '' -p <path to Zope.cgi>/Zope.cgi
|
||||
|
||||
where <path to Zope.cgi> is the (full) path to where Zope.cgi lives (see
|
||||
below). There now also should be a file in ${PREFIX}/etc/rc.d/ (most
|
||||
probably /usr/local/etc/rc.d/) named zope.sh that does the startup for you
|
||||
after a reboot.
|
||||
|
||||
Also, it might be a good idea now to change the password. You can do that
|
||||
with (again, in the Zope base directory):
|
||||
|
||||
python zpasswd.py -u <username> -p <passwd> -e CLEARTEXT access
|
||||
|
||||
The -e CLEARTEXT presently is *mandatory*, otherwise authentication
|
||||
through apache will not work.
|
||||
|
||||
You will probably already have gone through Apache's ssl certificate
|
||||
generation process. If not, please do so now, if you don't already have a
|
||||
certificate. If only a few well known people will have access to your
|
||||
management screens, a self-signed one probably will suffice. Please refer
|
||||
to the Apache and the Apache-SSL documentation for further information.
|
||||
Use a sufficiently "long" key. Don't forget the https://... when trying to
|
||||
access the management pages.
|
||||
|
||||
Apache will communicate with Zope through the so-called persistent cgi
|
||||
interface (aka pcgi). There's links to more information on the Zope web
|
||||
site at http://www.zope.org. Also, this is the best (and only) source of
|
||||
help end information on Zope itself.
|
||||
|
||||
Zope is Copyrighted (C) by Digital Creations. All rights reserved.
|
||||
Please thouroughly read the license (see below) before employing Zope.
|
||||
|
||||
Good business, Peter Cornelius. <pcc@gmx.net>
|
||||
|
||||
Please remember these files and directories:
|
||||
1
www/zope213/pkg-comment
Normal file
1
www/zope213/pkg-comment
Normal file
|
|
@ -0,0 +1 @@
|
|||
An object-based web application platform with database access
|
||||
25
www/zope213/pkg-descr
Normal file
25
www/zope213/pkg-descr
Normal file
|
|
@ -0,0 +1,25 @@
|
|||
Zope is Copyrighted (C) Digital Creations. All rights reserved. This is
|
||||
what they themselves say about it:
|
||||
|
||||
"Zope (WWW: http://www.zope.org/ ) is an exciting new object-based, open
|
||||
source web application platform. It allows you to build powerful and
|
||||
dynamic web applications easily. Zope comes with source code and is
|
||||
friendly to developers as well as users.
|
||||
Zope is distinguished by its integrated object database which, when
|
||||
combined with a revolutionary object model, provides a completely unique
|
||||
facility for servicing content managers and web application developers."
|
||||
|
||||
Here are some of the "headlines" mentioned in the features list at
|
||||
WWW: http://www.zope.org/Information/Features :
|
||||
|
||||
Database Integration Content Management
|
||||
SQL and HTML in Harmony Builtin Objects
|
||||
Multiple Data Sources Document Templates
|
||||
Publish Databases Web to Objects
|
||||
Application Development Integrated Object Database
|
||||
DTML Scripting Managed Through the Web
|
||||
External Methods Direct URL Access to Objects
|
||||
|
||||
This is a "beta" release. It seems to work quite stable, but no guarantee
|
||||
given.
|
||||
Peter Cornelius <pcc@gmx.net>
|
||||
1108
www/zope213/pkg-plist
Normal file
1108
www/zope213/pkg-plist
Normal file
File diff suppressed because it is too large
Load diff
82
www/zope28/Makefile
Normal file
82
www/zope28/Makefile
Normal file
|
|
@ -0,0 +1,82 @@
|
|||
# New ports collection makefile for: Zope
|
||||
# Version required: 2.0.1
|
||||
# Date created: Sat 21 Aug 1999
|
||||
# Whom: Peter Cornelius <pcc@gmx.net>
|
||||
#
|
||||
# $FreeBSD$
|
||||
|
||||
DISTNAME= Zope-${VERSION}-src
|
||||
PKGNAME= zope-${VERSION}
|
||||
CATEGORIES= www python
|
||||
MASTER_SITES= http://www.zope.org/Products/Zope/${VERSION}/
|
||||
EXTRACT_SUFX= .tgz
|
||||
|
||||
MAINTAINER= ports@FreeBSD.ORG
|
||||
|
||||
BUILD_DEPENDS= python1.5:${PORTSDIR}/lang/python
|
||||
RUN_DEPENDS= apache:${PORTSDIR}/www/apache13-modssl
|
||||
|
||||
# Build has to be done in the final location after installing the sources
|
||||
# there. It were a major action to fix all paths otherwise.
|
||||
do-build: # empty, but needs to be there for the python dependency.
|
||||
|
||||
# The web server's "root" directory used to be ${PREFIX}/www, and from
|
||||
# then on, data, cgi-bin and such. Thus, I decided that Zope belongs
|
||||
# there, too. I don't know whether this still applies to current apache
|
||||
# releases, though. I still run 2.2.8-STABLE.
|
||||
VERSION= 2.0.0b5
|
||||
PLIST_SUB= ZOPEBASEDIR=www/Zope-${VERSION} CGIBINDIR=share/apache/cgi-bin VERSION=${VERSION}
|
||||
WEBBASEDIR?= ${PREFIX}/www
|
||||
ZOPEBASEDIR?= ${WEBBASEDIR}/Zope-${VERSION}
|
||||
CGI_BIN_DIR?= ${PREFIX}/share/apache/cgi-bin
|
||||
APACHE_CONFDIR?= ${PREFIX}/etc/apache
|
||||
PYTHON15?= ${PREFIX}/bin/python1.5
|
||||
CHMOD= /bin/chmod
|
||||
|
||||
# I decided to consider the whole souce tree to be part of the package
|
||||
# since in there, Zope can live on its own. It does leave some *.o files
|
||||
# around (about four), but I can use Zope's own building mechanism.
|
||||
do-install: #
|
||||
@if [ -e ${ZOPEBASEDIR}/var/Data.fs ] ; then \
|
||||
${ECHO} "Saving existing Database to /tmp/Data.fs.BAK." ; \
|
||||
${MV} ${ZOPEBASEDIR}/var/Data.fs /tmp/Data.fs.BAK ; \
|
||||
fi
|
||||
@( ${MKDIR} ${ZOPEBASEDIR} ; \
|
||||
${ECHO} "===> Please be patient, some builds need their time." ; \
|
||||
${ECHO} "===> Copying..." ; \
|
||||
${CP} -Rp ${WRKSRC}/* ${ZOPEBASEDIR}/ ; \
|
||||
cd ${ZOPEBASEDIR} ; \
|
||||
${PYTHON15} w_pcgi.py ; \
|
||||
${PYTHON15} wo_pcgi.py ; \
|
||||
${MV} Zope.cgi Zope.cgi.orig ; \
|
||||
${ECHO} "#! ${CGI_BIN_DIR}/pcgi-wrapper" > Zope.cgi ; \
|
||||
${CAT} Zope.cgi.orig >> Zope.cgi ; \
|
||||
${INSTALL} -o nobody -m 555 Zope.cgi pcgi/pcgi-wrapper ${CGI_BIN_DIR} ; \
|
||||
${ECHO} "===> Fixing permissions of Zope's own var directory..." ; \
|
||||
${CHMOD} ugo+rwt var ; \
|
||||
${ECHO} "===> Setting user/password to zopemaster/test..." ; \
|
||||
${PYTHON15} zpasswd.py -u zopemaster -p test -e CLEARTEXT access ; \
|
||||
${ECHO} "===> Copying Apache config file changes to ${APACHE_CONFDIR}/apache.conf.Zope-${VERSION}-Changes." ; \
|
||||
${CP} -p ${FILESDIR}/apache.conf.Zope-${VERSION}-Changes ${APACHE_CONFDIR}/ ; \
|
||||
${ECHO} "===> Please have a look at this file and the instructions" ; \
|
||||
${ECHO} "===> therein and incorporate them to your apache.conf." ; \
|
||||
${ECHO} "===> Creating rc startup file for Zope-${VERSION}..." ; \
|
||||
${ECHO} "#! /bin/sh" > ${PREFIX}/etc/rc.d/zope.sh ; \
|
||||
${ECHO} "${ZOPEBASEDIR}/start -w '' -f '' -m '' -p ${CGI_BIN_DIR}/Zope.cgi &" >> ${PREFIX}/etc/rc.d/zope.sh ; \
|
||||
${ECHO} "echo -n \" Zope\"" >> ${PREFIX}/etc/rc.d/zope.sh ; \
|
||||
${CHMOD} ug+x,o-rwx ${PREFIX}/etc/rc.d/zope.sh ; \
|
||||
${ECHO} "===> Done with ${PREFIX}/etc/rc.d/zope.sh." ; \
|
||||
${CAT} ${FILESDIR}/Message ; \
|
||||
${ECHO} "===> Your Zope base directory is ${ZOPEBASEDIR}." ; \
|
||||
${ECHO} "===> The Zope license is in ${ZOPEBASEDIR}/LICENSE.txt." ; \
|
||||
${ECHO} "===> For Apache changes see ${APACHE_CONFDIR}/apache.conf.Zope-${VERSION}-Changes." ; \
|
||||
${ECHO} "===> Zope.cgi and pcgi-wrapper live in ${CGI_BIN_DIR}." )
|
||||
|
||||
#pre-deinstall: # Save Database contents. I expect /tmp to have sufficient
|
||||
# # space to hold it for the time being.
|
||||
# @if [ -e ${ZOPEBASEDIR}/var/Data.fs ] ; then \
|
||||
# ${ECHO} "Saving existing Database to /tmp/Data.fs.bak." ; \
|
||||
# ${MV} ${ZOPEBASEDIR}/var/Data.fs /tmp/Data.fs.bak ; \
|
||||
# fi
|
||||
|
||||
.include <bsd.port.mk>
|
||||
1
www/zope28/distinfo
Normal file
1
www/zope28/distinfo
Normal file
|
|
@ -0,0 +1 @@
|
|||
MD5 (Zope-2.0.0b5-src.tgz) = 22916a3b0852ee5eba3c2b42e160bc31
|
||||
6
www/zope28/files/CREDITS
Normal file
6
www/zope28/files/CREDITS
Normal file
|
|
@ -0,0 +1,6 @@
|
|||
Special thanks to (in no particular order):
|
||||
|
||||
- The Zope makers: Digital Creations.
|
||||
- The Python Group
|
||||
- Olaf Erb
|
||||
- Andreas Ley
|
||||
57
www/zope28/files/Message
Normal file
57
www/zope28/files/Message
Normal file
|
|
@ -0,0 +1,57 @@
|
|||
|
||||
Welcome to Zope.
|
||||
|
||||
The basic installation process for FreeBSD now has been done. To have a
|
||||
quick look, cd to your Zope base directory (see below) and start Zope
|
||||
with:
|
||||
|
||||
./start -w <web port> -f <ftp port>
|
||||
|
||||
where <web port> is the port where to http-access Zope with your browser
|
||||
(try http://localhost:<web port>). It defaults to 80. <ftp-port> is the
|
||||
same thing for ftp (upload) access, it defaults to 21. Obviously, you will
|
||||
have to specify these if you already use these ports. The user/password
|
||||
pair for access to the management screens has been preset to
|
||||
zopemaster/test, respectively.
|
||||
|
||||
PLEASE NOTE that the above only is for a quick check only, BUT IT WILL
|
||||
LEAVE YOUR ZOPE PROCESS WIDE OPEN TO HACKING SINCE THERE'S NO SECURITY
|
||||
WHATSOEVER. Therefore, PLEASE do incorporate the suggested changes (see
|
||||
below) to your apache-SSL web server and only start Zope WITHOUT ANY open
|
||||
<web port> or <ftp port>. This can be done, also from the Zope base dir,
|
||||
by:
|
||||
|
||||
./start -w '' -f '' -m '' -p <path to Zope.cgi>/Zope.cgi
|
||||
|
||||
where <path to Zope.cgi> is the (full) path to where Zope.cgi lives (see
|
||||
below). There now also should be a file in ${PREFIX}/etc/rc.d/ (most
|
||||
probably /usr/local/etc/rc.d/) named zope.sh that does the startup for you
|
||||
after a reboot.
|
||||
|
||||
Also, it might be a good idea now to change the password. You can do that
|
||||
with (again, in the Zope base directory):
|
||||
|
||||
python zpasswd.py -u <username> -p <passwd> -e CLEARTEXT access
|
||||
|
||||
The -e CLEARTEXT presently is *mandatory*, otherwise authentication
|
||||
through apache will not work.
|
||||
|
||||
You will probably already have gone through Apache's ssl certificate
|
||||
generation process. If not, please do so now, if you don't already have a
|
||||
certificate. If only a few well known people will have access to your
|
||||
management screens, a self-signed one probably will suffice. Please refer
|
||||
to the Apache and the Apache-SSL documentation for further information.
|
||||
Use a sufficiently "long" key. Don't forget the https://... when trying to
|
||||
access the management pages.
|
||||
|
||||
Apache will communicate with Zope through the so-called persistent cgi
|
||||
interface (aka pcgi). There's links to more information on the Zope web
|
||||
site at http://www.zope.org. Also, this is the best (and only) source of
|
||||
help end information on Zope itself.
|
||||
|
||||
Zope is Copyrighted (C) by Digital Creations. All rights reserved.
|
||||
Please thouroughly read the license (see below) before employing Zope.
|
||||
|
||||
Good business, Peter Cornelius. <pcc@gmx.net>
|
||||
|
||||
Please remember these files and directories:
|
||||
1
www/zope28/pkg-comment
Normal file
1
www/zope28/pkg-comment
Normal file
|
|
@ -0,0 +1 @@
|
|||
An object-based web application platform with database access
|
||||
25
www/zope28/pkg-descr
Normal file
25
www/zope28/pkg-descr
Normal file
|
|
@ -0,0 +1,25 @@
|
|||
Zope is Copyrighted (C) Digital Creations. All rights reserved. This is
|
||||
what they themselves say about it:
|
||||
|
||||
"Zope (WWW: http://www.zope.org/ ) is an exciting new object-based, open
|
||||
source web application platform. It allows you to build powerful and
|
||||
dynamic web applications easily. Zope comes with source code and is
|
||||
friendly to developers as well as users.
|
||||
Zope is distinguished by its integrated object database which, when
|
||||
combined with a revolutionary object model, provides a completely unique
|
||||
facility for servicing content managers and web application developers."
|
||||
|
||||
Here are some of the "headlines" mentioned in the features list at
|
||||
WWW: http://www.zope.org/Information/Features :
|
||||
|
||||
Database Integration Content Management
|
||||
SQL and HTML in Harmony Builtin Objects
|
||||
Multiple Data Sources Document Templates
|
||||
Publish Databases Web to Objects
|
||||
Application Development Integrated Object Database
|
||||
DTML Scripting Managed Through the Web
|
||||
External Methods Direct URL Access to Objects
|
||||
|
||||
This is a "beta" release. It seems to work quite stable, but no guarantee
|
||||
given.
|
||||
Peter Cornelius <pcc@gmx.net>
|
||||
1108
www/zope28/pkg-plist
Normal file
1108
www/zope28/pkg-plist
Normal file
File diff suppressed because it is too large
Load diff
82
www/zope29/Makefile
Normal file
82
www/zope29/Makefile
Normal file
|
|
@ -0,0 +1,82 @@
|
|||
# New ports collection makefile for: Zope
|
||||
# Version required: 2.0.1
|
||||
# Date created: Sat 21 Aug 1999
|
||||
# Whom: Peter Cornelius <pcc@gmx.net>
|
||||
#
|
||||
# $FreeBSD$
|
||||
|
||||
DISTNAME= Zope-${VERSION}-src
|
||||
PKGNAME= zope-${VERSION}
|
||||
CATEGORIES= www python
|
||||
MASTER_SITES= http://www.zope.org/Products/Zope/${VERSION}/
|
||||
EXTRACT_SUFX= .tgz
|
||||
|
||||
MAINTAINER= ports@FreeBSD.ORG
|
||||
|
||||
BUILD_DEPENDS= python1.5:${PORTSDIR}/lang/python
|
||||
RUN_DEPENDS= apache:${PORTSDIR}/www/apache13-modssl
|
||||
|
||||
# Build has to be done in the final location after installing the sources
|
||||
# there. It were a major action to fix all paths otherwise.
|
||||
do-build: # empty, but needs to be there for the python dependency.
|
||||
|
||||
# The web server's "root" directory used to be ${PREFIX}/www, and from
|
||||
# then on, data, cgi-bin and such. Thus, I decided that Zope belongs
|
||||
# there, too. I don't know whether this still applies to current apache
|
||||
# releases, though. I still run 2.2.8-STABLE.
|
||||
VERSION= 2.0.0b5
|
||||
PLIST_SUB= ZOPEBASEDIR=www/Zope-${VERSION} CGIBINDIR=share/apache/cgi-bin VERSION=${VERSION}
|
||||
WEBBASEDIR?= ${PREFIX}/www
|
||||
ZOPEBASEDIR?= ${WEBBASEDIR}/Zope-${VERSION}
|
||||
CGI_BIN_DIR?= ${PREFIX}/share/apache/cgi-bin
|
||||
APACHE_CONFDIR?= ${PREFIX}/etc/apache
|
||||
PYTHON15?= ${PREFIX}/bin/python1.5
|
||||
CHMOD= /bin/chmod
|
||||
|
||||
# I decided to consider the whole souce tree to be part of the package
|
||||
# since in there, Zope can live on its own. It does leave some *.o files
|
||||
# around (about four), but I can use Zope's own building mechanism.
|
||||
do-install: #
|
||||
@if [ -e ${ZOPEBASEDIR}/var/Data.fs ] ; then \
|
||||
${ECHO} "Saving existing Database to /tmp/Data.fs.BAK." ; \
|
||||
${MV} ${ZOPEBASEDIR}/var/Data.fs /tmp/Data.fs.BAK ; \
|
||||
fi
|
||||
@( ${MKDIR} ${ZOPEBASEDIR} ; \
|
||||
${ECHO} "===> Please be patient, some builds need their time." ; \
|
||||
${ECHO} "===> Copying..." ; \
|
||||
${CP} -Rp ${WRKSRC}/* ${ZOPEBASEDIR}/ ; \
|
||||
cd ${ZOPEBASEDIR} ; \
|
||||
${PYTHON15} w_pcgi.py ; \
|
||||
${PYTHON15} wo_pcgi.py ; \
|
||||
${MV} Zope.cgi Zope.cgi.orig ; \
|
||||
${ECHO} "#! ${CGI_BIN_DIR}/pcgi-wrapper" > Zope.cgi ; \
|
||||
${CAT} Zope.cgi.orig >> Zope.cgi ; \
|
||||
${INSTALL} -o nobody -m 555 Zope.cgi pcgi/pcgi-wrapper ${CGI_BIN_DIR} ; \
|
||||
${ECHO} "===> Fixing permissions of Zope's own var directory..." ; \
|
||||
${CHMOD} ugo+rwt var ; \
|
||||
${ECHO} "===> Setting user/password to zopemaster/test..." ; \
|
||||
${PYTHON15} zpasswd.py -u zopemaster -p test -e CLEARTEXT access ; \
|
||||
${ECHO} "===> Copying Apache config file changes to ${APACHE_CONFDIR}/apache.conf.Zope-${VERSION}-Changes." ; \
|
||||
${CP} -p ${FILESDIR}/apache.conf.Zope-${VERSION}-Changes ${APACHE_CONFDIR}/ ; \
|
||||
${ECHO} "===> Please have a look at this file and the instructions" ; \
|
||||
${ECHO} "===> therein and incorporate them to your apache.conf." ; \
|
||||
${ECHO} "===> Creating rc startup file for Zope-${VERSION}..." ; \
|
||||
${ECHO} "#! /bin/sh" > ${PREFIX}/etc/rc.d/zope.sh ; \
|
||||
${ECHO} "${ZOPEBASEDIR}/start -w '' -f '' -m '' -p ${CGI_BIN_DIR}/Zope.cgi &" >> ${PREFIX}/etc/rc.d/zope.sh ; \
|
||||
${ECHO} "echo -n \" Zope\"" >> ${PREFIX}/etc/rc.d/zope.sh ; \
|
||||
${CHMOD} ug+x,o-rwx ${PREFIX}/etc/rc.d/zope.sh ; \
|
||||
${ECHO} "===> Done with ${PREFIX}/etc/rc.d/zope.sh." ; \
|
||||
${CAT} ${FILESDIR}/Message ; \
|
||||
${ECHO} "===> Your Zope base directory is ${ZOPEBASEDIR}." ; \
|
||||
${ECHO} "===> The Zope license is in ${ZOPEBASEDIR}/LICENSE.txt." ; \
|
||||
${ECHO} "===> For Apache changes see ${APACHE_CONFDIR}/apache.conf.Zope-${VERSION}-Changes." ; \
|
||||
${ECHO} "===> Zope.cgi and pcgi-wrapper live in ${CGI_BIN_DIR}." )
|
||||
|
||||
#pre-deinstall: # Save Database contents. I expect /tmp to have sufficient
|
||||
# # space to hold it for the time being.
|
||||
# @if [ -e ${ZOPEBASEDIR}/var/Data.fs ] ; then \
|
||||
# ${ECHO} "Saving existing Database to /tmp/Data.fs.bak." ; \
|
||||
# ${MV} ${ZOPEBASEDIR}/var/Data.fs /tmp/Data.fs.bak ; \
|
||||
# fi
|
||||
|
||||
.include <bsd.port.mk>
|
||||
1
www/zope29/distinfo
Normal file
1
www/zope29/distinfo
Normal file
|
|
@ -0,0 +1 @@
|
|||
MD5 (Zope-2.0.0b5-src.tgz) = 22916a3b0852ee5eba3c2b42e160bc31
|
||||
6
www/zope29/files/CREDITS
Normal file
6
www/zope29/files/CREDITS
Normal file
|
|
@ -0,0 +1,6 @@
|
|||
Special thanks to (in no particular order):
|
||||
|
||||
- The Zope makers: Digital Creations.
|
||||
- The Python Group
|
||||
- Olaf Erb
|
||||
- Andreas Ley
|
||||
57
www/zope29/files/Message
Normal file
57
www/zope29/files/Message
Normal file
|
|
@ -0,0 +1,57 @@
|
|||
|
||||
Welcome to Zope.
|
||||
|
||||
The basic installation process for FreeBSD now has been done. To have a
|
||||
quick look, cd to your Zope base directory (see below) and start Zope
|
||||
with:
|
||||
|
||||
./start -w <web port> -f <ftp port>
|
||||
|
||||
where <web port> is the port where to http-access Zope with your browser
|
||||
(try http://localhost:<web port>). It defaults to 80. <ftp-port> is the
|
||||
same thing for ftp (upload) access, it defaults to 21. Obviously, you will
|
||||
have to specify these if you already use these ports. The user/password
|
||||
pair for access to the management screens has been preset to
|
||||
zopemaster/test, respectively.
|
||||
|
||||
PLEASE NOTE that the above only is for a quick check only, BUT IT WILL
|
||||
LEAVE YOUR ZOPE PROCESS WIDE OPEN TO HACKING SINCE THERE'S NO SECURITY
|
||||
WHATSOEVER. Therefore, PLEASE do incorporate the suggested changes (see
|
||||
below) to your apache-SSL web server and only start Zope WITHOUT ANY open
|
||||
<web port> or <ftp port>. This can be done, also from the Zope base dir,
|
||||
by:
|
||||
|
||||
./start -w '' -f '' -m '' -p <path to Zope.cgi>/Zope.cgi
|
||||
|
||||
where <path to Zope.cgi> is the (full) path to where Zope.cgi lives (see
|
||||
below). There now also should be a file in ${PREFIX}/etc/rc.d/ (most
|
||||
probably /usr/local/etc/rc.d/) named zope.sh that does the startup for you
|
||||
after a reboot.
|
||||
|
||||
Also, it might be a good idea now to change the password. You can do that
|
||||
with (again, in the Zope base directory):
|
||||
|
||||
python zpasswd.py -u <username> -p <passwd> -e CLEARTEXT access
|
||||
|
||||
The -e CLEARTEXT presently is *mandatory*, otherwise authentication
|
||||
through apache will not work.
|
||||
|
||||
You will probably already have gone through Apache's ssl certificate
|
||||
generation process. If not, please do so now, if you don't already have a
|
||||
certificate. If only a few well known people will have access to your
|
||||
management screens, a self-signed one probably will suffice. Please refer
|
||||
to the Apache and the Apache-SSL documentation for further information.
|
||||
Use a sufficiently "long" key. Don't forget the https://... when trying to
|
||||
access the management pages.
|
||||
|
||||
Apache will communicate with Zope through the so-called persistent cgi
|
||||
interface (aka pcgi). There's links to more information on the Zope web
|
||||
site at http://www.zope.org. Also, this is the best (and only) source of
|
||||
help end information on Zope itself.
|
||||
|
||||
Zope is Copyrighted (C) by Digital Creations. All rights reserved.
|
||||
Please thouroughly read the license (see below) before employing Zope.
|
||||
|
||||
Good business, Peter Cornelius. <pcc@gmx.net>
|
||||
|
||||
Please remember these files and directories:
|
||||
1
www/zope29/pkg-comment
Normal file
1
www/zope29/pkg-comment
Normal file
|
|
@ -0,0 +1 @@
|
|||
An object-based web application platform with database access
|
||||
25
www/zope29/pkg-descr
Normal file
25
www/zope29/pkg-descr
Normal file
|
|
@ -0,0 +1,25 @@
|
|||
Zope is Copyrighted (C) Digital Creations. All rights reserved. This is
|
||||
what they themselves say about it:
|
||||
|
||||
"Zope (WWW: http://www.zope.org/ ) is an exciting new object-based, open
|
||||
source web application platform. It allows you to build powerful and
|
||||
dynamic web applications easily. Zope comes with source code and is
|
||||
friendly to developers as well as users.
|
||||
Zope is distinguished by its integrated object database which, when
|
||||
combined with a revolutionary object model, provides a completely unique
|
||||
facility for servicing content managers and web application developers."
|
||||
|
||||
Here are some of the "headlines" mentioned in the features list at
|
||||
WWW: http://www.zope.org/Information/Features :
|
||||
|
||||
Database Integration Content Management
|
||||
SQL and HTML in Harmony Builtin Objects
|
||||
Multiple Data Sources Document Templates
|
||||
Publish Databases Web to Objects
|
||||
Application Development Integrated Object Database
|
||||
DTML Scripting Managed Through the Web
|
||||
External Methods Direct URL Access to Objects
|
||||
|
||||
This is a "beta" release. It seems to work quite stable, but no guarantee
|
||||
given.
|
||||
Peter Cornelius <pcc@gmx.net>
|
||||
1108
www/zope29/pkg-plist
Normal file
1108
www/zope29/pkg-plist
Normal file
File diff suppressed because it is too large
Load diff
Loading…
Add table
Reference in a new issue