From owner-freebsd-ports@FreeBSD.ORG Thu Jun 21 15:02:10 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 1BC871065697 for ; Thu, 21 Jun 2012 15:02:10 +0000 (UTC) (envelope-from xenophon+freebsd@irtnog.org) Received: from mx1.irtnog.org (rrcs-24-123-13-61.central.biz.rr.com [24.123.13.61]) by mx1.freebsd.org (Postfix) with ESMTP id DAAAF8FC0A for ; Thu, 21 Jun 2012 15:02:09 +0000 (UTC) Received: from cinep001bsdgw.irtnog.net (localhost [127.0.0.1]) by mx1.irtnog.org (Postfix) with ESMTP id AA704CEB9 for ; Thu, 21 Jun 2012 11:02:03 -0400 (EDT) X-Virus-Scanned: amavisd-new at irtnog.org Received: from mx1.irtnog.org ([127.0.0.1]) by cinep001bsdgw.irtnog.net (mx1.irtnog.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SW0K_F1uplmo for ; Thu, 21 Jun 2012 11:01:57 -0400 (EDT) Received: from cinip100ntsbs.irtnog.net (cinip100ntsbs.irtnog.net [10.63.1.100]) by mx1.irtnog.org (Postfix) with ESMTP for ; Thu, 21 Jun 2012 11:01:57 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 21 Jun 2012 11:01:54 -0400 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Need advice on a problems with the Django CMS port thread-index: Ac1PqO6gx+uPC7dQTyO7BKaSYbhhawACEhRA References: From: "xenophon\\+freebsd" To: 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 15:02:10 -0000 Thank you all for your feedback! > 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. In this case, OPTIONS_MULTI is correct. Django CMS can use one or more of those database backends. I'm going to turn on SQLite by default. One more question: Django CMS requires Django 1.3. It will not work with Django 1.4 or 1.2. How should I raise an error if Django 1.4 or 1.2 are already installed? I was thinking that I could use a RUN_DEPENDS entry similar to the following, and then let the www/py-django13 port's CONFLICTS do its thing. ${PYTHON_PKGNAMEPREFIX}django=3D1.3.1:${PORTSDIR}/www/py-django13 And many, many, many thanks to whoever came up with optionsng. Seriously - it fixes every annoyance I had with the old WITH/WITHOUT knobs and per-port configuration customization. Thank you. Best wishes, Matthew --=20 I FIGHT FOR THE USERS