From owner-freebsd-ports@FreeBSD.ORG Thu Jun 21 12:18:04 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1E401065675 for ; Thu, 21 Jun 2012 12:18:04 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 7E3F18FC14 for ; Thu, 21 Jun 2012 12:18:04 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q5LCI3DG070488; Thu, 21 Jun 2012 06:18:03 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q5LCI3OH070485; Thu, 21 Jun 2012 06:18:03 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Thu, 21 Jun 2012 06:18:03 -0600 (MDT) From: Warren Block To: Scot Hetzel In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-902635197-61246561-1340281083=:70177" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Thu, 21 Jun 2012 06:18:04 -0600 (MDT) Cc: "xenophon\\+freebsd" , freebsd-ports@freebsd.org Subject: Re: Need advice on a problems with the Django CMS port X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2012 12:18:05 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---902635197-61246561-1340281083=:70177 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8BIT On Thu, 21 Jun 2012, Scot Hetzel wrote: > On Thu, Jun 21, 2012 at 12:14 AM, Scot Hetzel wrote: >> On Wed, Jun 20, 2012 at 11:38 PM, xenophon\+freebsd >> wrote: >>> Hi all, >>> >>> I maintain the Django CMS port (www/py-django-cms).  I could use some >>> advice on the following problem both from other maintainers and from >>> other users of the ports tree: >>> >>> Django CMS requires a database backend, which it accesses through the >>> Django web app framework.  The Django port (www/py-django) doesn't >>> include database support by default.  If someone naively runs "cd >>> /usr/ports/www/py-django-cms; make install", Django CMS won't work >>> properly because of the missing database drivers.  The Django port does >>> have knobs for PostgreSQL, MySQL, and SQLite, but those knobs don't >>> affect what bits of Django get installed.  All the knobs do is add >>> databases/{py-psycopg2,py-MySQLdb,py-sqlite3} to the Django package's >>> RUN_DEPENDS.  As I see it, I have the following options: >>> >> : >>> (c) I could add knobs to the Django CMS port similar to those found in >>> the Django port (i.e., add to RUN_DEPENDS if knob is set) - >>> functionally, it doesn't matter which port pulls in the required >>> database drivers.  This is probably the most user friendly, in that a >>> single run of "make install" will result in a working version of Django >>> CMS. >>> >>> I think option (c) is the best, but I'd love to hear what the community >>> thinks. >>> >> Option C would be the best, as the port depends on a database (MySQL, >> PostgreSQL or SQLite). >> >> I believe the following would work with the new options framework: >> >> OPTIONS_MULTI=          DATABASE >> OPTIONS_MULTI_DATABASE= MYSQL PGSQL SQLITE > > This should be OPTIONS_SINGLE and OPTIONS_SINGLE_DATABASE, as you only > need one of these. Depends on the port. If it can use more than one database system at a time, then the OPTIONS_MULTI "at least one of these" would be right. ---902635197-61246561-1340281083=:70177--