Date: Thu, 21 Jun 2012 06:18:03 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Scot Hetzel <swhetzel@gmail.com> Cc: "xenophon\\+freebsd" <xenophon+freebsd@irtnog.org>, freebsd-ports@freebsd.org Subject: Re: Need advice on a problems with the Django CMS port Message-ID: <alpine.BSF.2.00.1206210614040.70177@wonkity.com> In-Reply-To: <CACdU%2Bf_rdeyUMCaKqjVR26F=AjoURBRetNXV77y9ZjtV7UEOTw@mail.gmail.com> References: <BABF8C57A778F04791343E5601659908236C2F@cinip100ntsbs.irtnog.net> <CACdU%2Bf_fYzeC9m8HkZhgTaMyzbMGJFjdw-fncZuSviT1KmnMCw@mail.gmail.com> <CACdU%2Bf_rdeyUMCaKqjVR26F=AjoURBRetNXV77y9ZjtV7UEOTw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <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). 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1206210614040.70177>