Date: Thu, 21 Jun 2012 00:20:24 -0500 From: Scot Hetzel <swhetzel@gmail.com> To: "xenophon\\+freebsd" <xenophon+freebsd@irtnog.org> Cc: freebsd-ports@freebsd.org Subject: Re: Need advice on a problems with the Django CMS port Message-ID: <CACdU%2Bf_rdeyUMCaKqjVR26F=AjoURBRetNXV77y9ZjtV7UEOTw@mail.gmail.com> In-Reply-To: <CACdU%2Bf_fYzeC9m8HkZhgTaMyzbMGJFjdw-fncZuSviT1KmnMCw@mail.gmail.com> References: <BABF8C57A778F04791343E5601659908236C2F@cinip100ntsbs.irtnog.net> <CACdU%2Bf_fYzeC9m8HkZhgTaMyzbMGJFjdw-fncZuSviT1KmnMCw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jun 21, 2012 at 12:14 AM, Scot Hetzel <swhetzel@gmail.com> wrote:
> On Wed, Jun 20, 2012 at 11:38 PM, xenophon\+freebsd
> <xenophon+freebsd@irtnog.org> wrote:
>> Hi all,
>>
>> I maintain the Django CMS port (www/py-django-cms). =A0I 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. =A0The Django port (www/py-django) doesn't
>> include database support by default. =A0If someone naively runs "cd
>> /usr/ports/www/py-django-cms; make install", Django CMS won't work
>> properly because of the missing database drivers. =A0The Django port doe=
s
>> have knobs for PostgreSQL, MySQL, and SQLite, but those knobs don't
>> affect what bits of Django get installed. =A0All the knobs do is add
>> databases/{py-psycopg2,py-MySQLdb,py-sqlite3} to the Django package's
>> RUN_DEPENDS. =A0As 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. =A0This 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=3D =A0 =A0 =A0 =A0 =A0DATABASE
> OPTIONS_MULTI_DATABASE=3D MYSQL PGSQL SQLITE
This should be OPTIONS_SINGLE and OPTIONS_SINGLE_DATABASE, as you only
need one of these.
>
> OPTIONS_DEFAULT=3D =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0SQLITE
>
> .include <bsd.port.options.mk>
>
> .if ${PORT_OPTIONS:MMYSQL}
> RUN_DEPENDS+=3D =A0 ${PYTHON_PKGNAMEPREFIX}MySQLdb>=3D1.2.2:${PORTSDIR}/d=
atabases/py-MySQLdb
> .endif
>
> .if ${PORT_OPTIONS:MPGSQL}
> RUN_DEPENDS+=3D =A0 ${PYTHON_SITELIBDIR}/psycopg2/_psycopg.so:${PORTSDIR}=
/databases/py-psycopg2
> .endif
> .if ${PORT_OPTIONS:MSQLITE}
> RUN_DEPENDS+=3D =A0 ${PYTHON_SITELIBDIR}/_sqlite3.so:${PORTSDIR}/database=
s/py-sqlite3
> .endif
> :
> :
> .include <bsd.port.mk>
>
> Scot
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACdU%2Bf_rdeyUMCaKqjVR26F=AjoURBRetNXV77y9ZjtV7UEOTw>