Date: Thu, 21 Jun 2012 11:01:54 -0400 From: "xenophon\\+freebsd" <xenophon+freebsd@irtnog.org> To: <freebsd-ports@freebsd.org> Subject: RE: Need advice on a problems with the Django CMS port Message-ID: <BABF8C57A778F04791343E5601659908236C30@cinip100ntsbs.irtnog.net> In-Reply-To: <alpine.BSF.2.00.1206210614040.70177@wonkity.com> References: <BABF8C57A778F04791343E5601659908236C2F@cinip100ntsbs.irtnog.net><CACdU%2Bf_fYzeC9m8HkZhgTaMyzbMGJFjdw-fncZuSviT1KmnMCw@mail.gmail.com><CACdU%2Bf_rdeyUMCaKqjVR26F=AjoURBRetNXV77y9ZjtV7UEOTw@mail.gmail.com> <alpine.BSF.2.00.1206210614040.70177@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BABF8C57A778F04791343E5601659908236C30>