From owner-freebsd-ports Tue Jun 13 17: 7:24 2000 Delivered-To: freebsd-ports@freebsd.org Received: from dorothy.hentschel.net (216-59-4-104.usa.flashcom.net [216.59.4.104]) by hub.freebsd.org (Postfix) with ESMTP id 268CB37B5DE; Tue, 13 Jun 2000 17:07:22 -0700 (PDT) (envelope-from thomas@hentschel.net) Received: from hentschel.net (thomas@falcon.home.hentschel.net [192.168.1.2]) by dorothy.hentschel.net (8.8.8/8.8.8) with ESMTP id QAA19931; Tue, 13 Jun 2000 16:55:36 -0700 (PDT) (envelope-from thomas@hentschel.net) Message-Id: <200006132355.QAA19931@dorothy.hentschel.net> Date: Tue, 13 Jun 2000 17:14:56 -0700 (PDT) From: thomas@hentschel.net Subject: Zope port revamp [was ports/18444: zope port outdated] To: steve@FreeBSD.org Cc: freebsd-ports@FreeBSD.org In-Reply-To: <200005290250.TAA41586@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just talking to several Zope/FreeBSD users on IRC, and we thought a bit of a revamp for this port is in order. Some background: Zope is a extensible application server created by Digital Creations. As this, it heavily relies on plug-ins, called "Products" in Zope lingo. I.e. there is a product called "SquishDot" which will turn a zope server into a Slashdot like forum within minutes. There are other products (Shopping carts, Portal Site kit, an Auction site etc, you name it, the total number of usable products is ~ 50) which don't come with a Zope distribution per se, but can be installed rather easily. In addition, there is a "Super" zope server (called ZEO) just around the corner. In order to make all that easily install-able and accessible from within FreeBSD, I thought of using the ports system. For that I would have to create a separate zope section (/usr/ports/zope). Is that something which sounds feasible ? If so, I'll submit a patch for the upcoming Zope-2.2.0 release with that functionality. -Th To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message