From owner-svn-ports-head@FreeBSD.ORG Tue Dec 10 10:31:51 2013 Return-Path: Delivered-To: svn-ports-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B5C63E1C; Tue, 10 Dec 2013 10:31:51 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A1BB51D47; Tue, 10 Dec 2013 10:31:51 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id rBAAVp1J087440; Tue, 10 Dec 2013 10:31:51 GMT (envelope-from koobs@svn.freebsd.org) Received: (from koobs@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id rBAAVpxP087439; Tue, 10 Dec 2013 10:31:51 GMT (envelope-from koobs@svn.freebsd.org) Message-Id: <201312101031.rBAAVpxP087439@svn.freebsd.org> From: Kubilay Kocak Date: Tue, 10 Dec 2013 10:31:51 +0000 (UTC) To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r336056 - head/www/py-django-dpaste X-SVN-Group: ports-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Dec 2013 10:31:51 -0000 Author: koobs Date: Tue Dec 10 10:31:51 2013 New Revision: 336056 URL: http://svnweb.freebsd.org/changeset/ports/336056 Log: www/py-django-dpaste: Add option for MIGRATIONS support (via south) A few migrations come packaged with this Django application and the author notes they are "preferred", but not required. Regarding the option naming, it was furiously debated in #freebsd-python and I opted for naming the "feature that is enabled" rather than the application enabling it. Another data point is the common use of the term "schema migrations" in Django parlance. Thank you xmj for being a great sounding board as always! Reported by: Johannes Meixner (xmj, via IRC) Reviewed by: Johannes Meixner Modified: head/www/py-django-dpaste/Makefile Modified: head/www/py-django-dpaste/Makefile ============================================================================== --- head/www/py-django-dpaste/Makefile Tue Dec 10 10:13:13 2013 (r336055) +++ head/www/py-django-dpaste/Makefile Tue Dec 10 10:31:51 2013 (r336056) @@ -16,6 +16,11 @@ RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}djan ${PYTHON_PKGNAMEPREFIX}pygments>=1.6:${PORTSDIR}/textproc/py-pygments \ ${PYTHON_PKGNAMEPREFIX}requests>=1.0.0:${PORTSDIR}/www/py-requests +OPTIONS_DEFINE= MIGRATIONS + +MIGRATIONS_DESC= Schema and data migration support (via south) +MIGRATIONS_RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}south>=0.8.2:${PORTSDIR}/databases/py-south + USE_GITHUB= yes USE_PYTHON= yes USE_PYDISTUTILS= easy_install