RE: www/py-django-cms [ID#2013012709000701]
Hi Carlo! There are several Django-related ports that need updating. I'm currently re-creating my build host and should have updated versions ready later this week or early next. Best wishes, Matthew -- I FIGHT FOR THE USERS -Original Message- From: Carlo Strub [mailto:c...@freebsd.org] Sent: Sunday, January 27, 2013 3:10 PM To: xenophon\+fbsdports Subject: www/py-django-cms [ID#2013012709000701] Hi, Did you see that there was a security vulnerability found in django-cms 2.3.5 (http://www.vuxml.org/freebsd/3886cafe-668c-11e2-94b8- 1c4bd681f0cf.html)? Please update the port as soon as possible. If you are busy or don't want to do it for other reasons, please tell me. Best, Carlo -- Carlo Strub Ports committer pub 3072R/D06F0BD7 2012-11-25 [expires: 2017-11-24] Key fingerprint = 61A4 F2B8 2A6C B81E 5557 0798 78E7 DE70 D06F 0BD7 uid Carlo Strub c...@carlostrub.ch uid Carlo Strub c...@freebsd.org sub 3072R/71C75997 2012-11-25 [expires: 2017-11-24] sub 3072R/318AEB16 2012-11-25 [expires: 2017-11-24] -- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
RE: Need advice on a problems with the Django CMS port
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=1.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
--
I FIGHT FOR THE USERS
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Need advice on a problems with the Django CMS port
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:
(a) I could add a warning to www/py-django-cms/pkg-message that says
something to the effect of make sure you build Django with database
support. This is the easiest thing for me to do, but it isn't very
user friendly.
(b) I could try to come up with some pre-installation test code that
checks for a working database backend in Django and then prompt the user
to re-build Django with database support. I have no idea how to do this
in a reliable way, but this is no less user friendly than having a port
set BROKEN or IGNORE when certain knobs are frobbed.
(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.
Best wishes,
Matthew
P.S. If you want to try out Django CMS, make sure you install Django
1.3. I'm going to update the Django CMS port to reflect this
requirement RSN.
--
I FIGHT FOR THE USERS
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Missing devel/php5-pcre package?
Hi, I'm upgrading from PHP 4 to the latest PHP 5 port, but I can't find a port for the PCRE module. There's an old port named devel/php52-pcre, but nothing that matches the current version. Best wishes, Matthew -- I FIGHT FOR THE USERS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
RE: Missing devel/php5-pcre package?
-Original Message- From: xenophon\+freebsd Sent: Saturday, May 19, 2012 9:51 AM I'm upgrading from PHP 4 to the latest PHP 5 port, but I can't find a port for the PCRE module. Whoops, never mind. It looks like PCRE is built into PHP 5.4 now. In any case, my app (OpenID-LDAP) works as expected. Best wishes, Matthew -- I FIGHT FOR THE USERS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
