| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Approved by: tcberner (mentor)
Differential Revision: https://reviews.freebsd.org/D16437
|
|
|
|
|
| |
Approved by: rihaz.jerrin@gmail.com (maintainer), tcberner (mentor)
Differential Revision: https://reviews.freebsd.org/D15824
|
|
|
|
| |
With hat: portmgr
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
PR: 218227
Submitted by: Rihaz Jerrin <rihaz.jerrin@gmail.com> (maintainer)
Approved by: lme (mentor)
Differential Revision: https://reviews.freebsd.org/D10204
|
|
|
|
|
|
| |
- While here, minor cosmetic and license fixes
Approved by: portmgr blanket
|
|
Check all NS Records for Zone Transfers.
Enumerate General DNS Records for a given
Domain (MX, SOA, NS, A, AAAA, SPF and TXT).
Perform common SRV Record Enumeration.
Top Level Domain (TLD) Expansion.
Check for Wildcard Resolution.
Brute Force subdomain and host A
and AAAA records given a domain and a wordlist.
Perform a PTR Record lookup for a given IP Range or CIDR.
Check a DNS Server Cached records for A, AAAA and
CNAME Records provided a list of host records in a text file to check.
Enumerate Common mDNS records in the Local
Network Enumerate Hosts and Subdomains using Google.
WWW: https://github.com/darkoperator/dnsrecon
PR: 208975
Submitted by: Rihaz Jerrin <rihaz.jerrin@gmail.com>
|