| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Notes:
svn path=/head/; revision=493808
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
Notes:
svn path=/head/; revision=487272
|
|
|
|
| |
Notes:
svn path=/head/; revision=476507
|
|
|
|
| |
Notes:
svn path=/head/; revision=470797
|
|
|
|
|
|
|
| |
version 1.1.0 (via revision 464079).
Notes:
svn path=/head/; revision=464084
|
|
|
|
| |
Notes:
svn path=/head/; revision=455337
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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=431014
|
|
|
|
|
|
|
|
| |
- Ignore py-rekall_gui: doesn't work with py-rekall-core 1.6.0 yet
- Ignore py-rekall: requires ipython 5.0.0
Notes:
svn path=/head/; revision=430814
|
|
|
|
|
|
|
|
|
|
| |
PR: 213743
Submitted by: mat
Exp-run by: antoine
Sponsored by: Absolight
Notes:
svn path=/head/; revision=425174
|
|
|
|
| |
Notes:
svn path=/head/; revision=418626
|
|
|
|
| |
Notes:
svn path=/head/; revision=417028
|
|
|
|
| |
Notes:
svn path=/head/; revision=413440
|
|
|
|
|
|
|
|
| |
With hat: portmgr
Sponsored by: Absolight
Notes:
svn path=/head/; revision=412349
|
|
|
|
|
|
|
|
|
|
| |
- Bump revisions of all dependant ports
PR: 206482
Submitted by: lev, w.schwarzenfeld@aon.at
Notes:
svn path=/head/; revision=411691
|
|
|
|
|
|
|
|
|
|
| |
It was split in 3 modules
- security/py-rekall-core : CORE component with command line interface
- security/py-rekall_gui : GUI with ipython and web interface
- security/py-rekall : "meta" module
Notes:
svn path=/head/; revision=396604
|
|
|
|
|
|
|
|
| |
Approved by: portmgr blanket
MFH: 2015Q2
Notes:
svn path=/head/; revision=388714
|
|
|
|
| |
Notes:
svn path=/head/; revision=384859
|
|
|
|
|
|
|
| |
Announce: http://rekall-forensic.blogspot.ch/2015/04/announcing-rekall-release-131-dammastock.html
Notes:
svn path=/head/; revision=383030
|
|
|
|
| |
Notes:
svn path=/head/; revision=375198
|
|
The Rekall Framework is a completely open collection of tools, implemented in
Python under the GNU General Public License, for the extraction of digital
artifacts from volatile memory (RAM) samples. The extraction techniques are
performed completely independent of the system being investigated but offer
visibility into the runtime state of the system. The framework is intended to
introduce people to the techniques and complexities associated with extracting
digital artifacts from volatile memory samples and provide a platform for
further work into this exciting area of research.
WWW: http://www.rekall-forensic.com/
Notes:
svn path=/head/; revision=370110
|