| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
While there, cleanup, and sort depends.
When build and run dependencies are the same, there are three ways to
avoid duplicating the list while not adding the framework added
BUILD_DEPENDS to the RUN_DEPENDS. In order of preference, they are:
1) use RUN_DEPENDS to set BUILD_DEPENDS:
BUILD_DEPENDS= ${RUN_DEPENDS}
RUN_DEPENDS= foo:bar/baz
2) create another variable and use it:
MY_DEPENDS= foo:bar/baz
BUILD_DEPENDS= ${MY_DEPENDS}
RUN_DEPENDS= ${MY_DEPENDS}
3) use BUILD_DEPENDS to set RUN_DEPENDS and force evaluation:
BUILD_DEPENDS= foo:bar/baz
RUN_DEPENDS:= ${BUILD_DEPENDS}
Sponsored by: Absolight
|
| |
|
|
|
|
|
| |
FLAVOR is the current port's flavor, it should not be used outside of
this scope.
Sponsored by: Absolight
|
| |
|
|
|
|
|
| |
they now redirect to anyway. All new urls checked to return 200,
I've fixed a couple of them in the process.
Approved by: portmgr blanket, mat
|
| |
|
|
|
| |
- Add regression tests
- Patch py-pyhwp to use olefile instead of legacy and removed OleFileIO_PL
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
| |
With hat: portmgr
Sponsored by: Absolight
|
| |
|
|
| |
- Bump PORTREVISION
|
| |
|
|
| |
- Bump PORTREVISION
|
|
|
Analyze and extract internal streams out from a HWP Document Format v5 file
Includes (experimental) Conversion to OpenDocument format (.odt) or plain
text (.txt)
WWW: https://pypi.python.org/pypi/pyhwp
|
