non port: devel/py-repoze.what/Makefile |
Number of commits found: 11 |
Friday, 25 Sep 2020
|
06:57 wen
- Mark DEPRECATED
|
Wednesday, 20 Jun 2018
|
17:05 mat
Use PY_FLAVOR for dependencies.
FLAVOR is the current port's flavor, it should not be used outside of
this scope.
Sponsored by: Absolight
|
Thursday, 30 Nov 2017
|
15:50 mat
Convert Python ports to FLAVORS.
Ports using USE_PYTHON=distutils are now flavored. They will
automatically get flavors (py27, py34, py35, py36) depending on what
versions they support.
There is also a USE_PYTHON=flavors for ports that do not use distutils
but need FLAVORS to be set. A USE_PYTHON=noflavors can be set if
using distutils but flavors are not wanted.
A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
added to cope with Python ports that did not have the Python
PKGNAMEPREFIX but are flavored.
USES=python now also exports a PY_FLAVOR variable that contains the
current python flavor. It can be used in dependency lines when the
port itself is not python flavored. For example, deskutils/calibre.
By default, all the flavors are generated. To only generate flavors
for the versions in PYTHON2_DEFAULT and PYTHON3_DEFAULT, define
BUILD_DEFAULT_PYTHON_FLAVORS in your make.conf.
In all the ports with Python dependencies, the *_DEPENDS entries MUST
end with the flavor so that the framework knows which to build/use.
This is done by appending '@${PY_FLAVOR}' after the origin (or
@${FLAVOR} if in a Python module with Python flavors, as the content
will be the same). For example:
RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}six>0:devel/py-six@${PY_FLAVOR}
PR: 223071
Reviewed by: portmgr, python
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D12464
|
Friday, 1 Apr 2016
|
14:00 mat
Remove ${PORTSDIR}/ from dependencies, categories d, e, f, and g.
With hat: portmgr
Sponsored by: Absolight
|
Monday, 20 Oct 2014
|
16:04 mva
- Convert ports of devel/ to USES=python
Approved by: portmgr (implicit)
|
Sunday, 8 Jun 2014
|
16:30 mva
- Remove easy_install dependency
- Convert to PYDISTUTILS_AUTOPLIST
- Bump PORTREVISION to enforce a cleanup for the easy_install references
With hat: python@
Approved by: portmgr (implicit)
|
Monday, 12 May 2014
|
01:25 gerald
- Staging.
- Tweak WWW line in pkg-descr.
PR: 188556
Submitted by: Bartek Rutkowski <ports@robakdesign.com>
Approved by: portmgr (blanket pre-approval)
|
Friday, 20 Sep 2013
|
17:13 bapt
Add NO_STAGE all over the place in preparation for the staging support (cat:
devel part 3)
|
Saturday, 21 Jan 2012
|
17:40 eadler
At the moment 1385 ports use BUILD_DEPENDS= ${RUN_DEPENDS} and 450
ports use BUILD_DEPENDS:= ${RUN_DEPENDS}. This patch fixes ports that are
currently broken. This is a temporary measure until we organically stop using
:= or someone(s) spend a lot of time changing all the ports over.
Explicit duplication > := > = and this just moves ports one step to the left
Approved by: portmgr
|
Wednesday, 7 Apr 2010
|
13:48 wen
- Update to 1.0.9
- Update my email to FreeBSD
|
Friday, 7 Aug 2009
|
20:09 miwi
repoze.what is an authorization framework for WSGI applications,
based on repoze.who (which deals with authentication and
identification).
On the one hand, it enables an authorization system based on the
groups to which the `authenticated or anonymous` user belongs and
the permissions granted to such groups by loading these groups
and permissions into the request on the way in to the downstream
WSGI application.
And on the other hand, it enables you to manage your groups and
permissions from the application itself or another program, under
a backend-independent API. For example, it would be easy for you
to switch from one back-end to another, and even use this framework
to migrate the data.
WWW: http://what.repoze.org/docs/1.x/
PR: ports/137459
Submitted by: Wen Heping <wenheping at gmail.com>
|
Number of commits found: 11 |