| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
| |
Notes:
svn path=/head/; revision=559287
|
|
|
|
| |
Notes:
svn path=/head/; revision=552233
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
tar: Pathname can't be converted from UTF-8 to current locale.
tar: Error exit delayed from previous errors.
*** Error code 1
See more details for the same issue in bug 246618.
Reported by: pkg-fallout
Approved by: portmgr blanket
Notes:
svn path=/head/; revision=543918
|
|
|
|
| |
Notes:
svn path=/head/; revision=541441
|
|
|
|
| |
Notes:
svn path=/head/; revision=534832
|
|
|
|
| |
Notes:
svn path=/head/; revision=527469
|
|
|
|
| |
Notes:
svn path=/head/; revision=524040
|
|
|
|
|
|
|
| |
- Drop python 2.7 support
Notes:
svn path=/head/; revision=518323
|
|
|
|
| |
Notes:
svn path=/head/; revision=506758
|
|
|
|
| |
Notes:
svn path=/head/; revision=503455
|
|
|
|
| |
Notes:
svn path=/head/; revision=501293
|
|
|
|
| |
Notes:
svn path=/head/; revision=492041
|
|
|
|
| |
Notes:
svn path=/head/; revision=487916
|
|
|
|
| |
Notes:
svn path=/head/; revision=481454
|
|
|
|
|
|
|
|
| |
- Now works with python 3
- Allow concurrent installation
Notes:
svn path=/head/; revision=473883
|
|
|
|
| |
Notes:
svn path=/head/; revision=470783
|
|
|
|
| |
Notes:
svn path=/head/; revision=457699
|
|
|
|
| |
Notes:
svn path=/head/; revision=457106
|
|
|
|
| |
Notes:
svn path=/head/; revision=455373
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
Notes:
svn path=/head/; revision=455210
|
|
|
|
| |
Notes:
svn path=/head/; revision=447471
|
|
|
|
| |
Notes:
svn path=/head/; revision=438036
|
|
|
|
|
|
|
| |
- Make it easier to test python 3 readiness
Notes:
svn path=/head/; revision=436444
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
locale set by the user. Add LANG=C and LC_ALL=C at the beginning of
bsd.port.mk and export them so all commands are executed with the C locale.
LC_ALL=C overrides all other LC_* variables. LANG is used by setlocale(3)
as default value for LC_* variables, so normally it isn't used when LC_ALL
is set, but there's code out there that looks at LANG directly so it's safer
to set it as well. The only commands not captured by this are !=
assignments before any inclusion of bsd.port.*mk.
Introduce USE_LOCALE=<locale> that adds LANG=<locale> and LC_ALL=<locale> to
CONFIGURE_ENV and MAKE_ENV so upstream build systems can be executed with a
different locale (e.g. USE_LOCALE=en_US.UTF-8).
PR: 215882
Exp-run by: antoine
Approved by: portmgr (antoine)
Notes:
svn path=/head/; revision=431796
|
|
|
|
| |
Notes:
svn path=/head/; revision=422523
|
|
|
|
|
|
|
|
| |
With hat: portmgr
Sponsored by: Absolight
Notes:
svn path=/head/; revision=412349
|
|
|
|
|
|
|
|
|
| |
precision for *time_nano fields. Adjust py-dfvfs for this.
See: https://github.com/log2timeline/dfvfs/issues/116
Notes:
svn path=/head/; revision=410715
|
|
|
|
| |
Notes:
svn path=/head/; revision=407089
|
|
|
|
| |
Notes:
svn path=/head/; revision=392899
|
|
|
|
| |
Notes:
svn path=/head/; revision=378247
|
|
|
|
| |
Notes:
svn path=/head/; revision=376573
|
|
|
|
| |
Notes:
svn path=/head/; revision=375135
|
|
|
|
| |
Notes:
svn path=/head/; revision=374166
|
|
|
|
| |
Notes:
svn path=/head/; revision=372386
|
|
|
|
| |
Notes:
svn path=/head/; revision=371766
|
|
|
|
| |
Notes:
svn path=/head/; revision=370006
|
|
|
|
| |
Notes:
svn path=/head/; revision=366136
|
|
|
|
| |
Notes:
svn path=/head/; revision=365506
|
|
|
|
| |
Notes:
svn path=/head/; revision=363634
|
|
|
|
| |
Notes:
svn path=/head/; revision=356687
|
|
dfVFS, or Digital Forensics Virtual File System, provides read-only access to
file-system objects from various storage media types and file formats. The goal
of dfVFS is to provide a generic interface for accessing file-system objects,
for which it uses several back-ends that provide the actual implementation of
the various storage media types, volume systems and file systems.
WWW: https://code.google.com/p/dfvfs/
Notes:
svn path=/head/; revision=355856
|