- Remove FLAVOR from py-docutils dependency in comms/uhd, in this case
it needs the rst2html command, not the docutils module
- Mark some ports as not compatible with python3
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
armv7, mark them so.
This is part two of a multipart commit to bring armv7 ports to parity
with armv6.
Approved by: portmgr (tier-2 blanket)
Obtained from: lonesome.com -exp run
Availability release of WSJT-X Version 1.8.0.
Changes since "Release Candidate 3" (wsjtx-1.8.0-rc3) are very minor; they are
described in the Release Notes posted here:
http://physics.princeton.edu/pulsar/k1jt/Release_Notes_1.8.0.txt
Installation packages for Windows, Linux, Macintosh, and Raspian Jessie
have been posted on the WSJT web site here:
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
You can also download the packages from our SourceForge site:
https://sourceforge.net/projects/wsjt/files/wsjtx-1.8.0-rc3/
(It may take a short time for the SourceForge site to be updated.)
If you are upgrading from -rc1, you will need to do a one-time reset of
the default list of suggested operating frequencies. Go to
*File->Settings->Frequencies*, right click on the table and select *Reset*.
We hope you will enjoy using WSJT-X Version 1.8.0.
-- 73, Joe, K1JT, for the WSJT Development Group
removed, I did miss that one. (It's directly used as a filename)
The other places are do not cares.
- It makes no sense to remove gets() without removing potentially
just as bad scanf() calls and it's bad practice to use scanf anyway
I'm paranoid with implementations of fgets() (Non FreeBSD to be clear)
hence the use of -1 in the length argument of fgets().
- I'll see if upstream is willing to accept these diffs.
Submitted by: Max Khon <fjoe@freebsd.org>
Reported by: Max Khon <fjoe@freebsd.org>
Simple TTY terminal application which features a straightforward
commandline interface to easily connect to TTY devices for basic
input/output.
WWW: https://tio.github.io
PR: 222719
Submitted by: Dmitri Goutnik <dg@syrec.org>
and act as the dx cluster client for fldigi. Multiple instances of flcluster
can simultaneously connect to fldigi, and fldigi's internal dx cluster client
can also be connected at the same time. Connectivity is via a socket interface,
so flclient can reside on the same or a different computer on the LAN or WAN
so long as it is possible to establish the socket (xmlrpc) connection.
On line help is available <http://www.w1hkj.com/flcluster-help/>
libzip was updated to 1.3.0 in r450774, and its SOVERSION went from .4 to .5
after the removal of zip_archive_set_tempdir(). All dependent ports continue to
build fine without that symbol.
PR: 222638
FTdX5000 mods
* fix scaling of power out and swr meters
mingw-mods
* modifications to allow building on Windows MinGW/Msys
xml inhibit
* inhibit both client and server xml i/o until transceiver fully initialized
WX HamQth bug fix
* Fixed access to remote data for Metar and HamQth queries
win7 mingw build fixes
* PRI?SZ format specifiers not recognized on all build platforms
wefax ui mods
wefax_map
* Create unique wefax mapping widget based on pre 3.23 picture widget
. resolution of new picture widget resize fault during wefax Rx
auto start
* add delays to allow sufficient time for external process to become stable
(via Mk/bsd.default-versions.mk and lang/gcc) which has moved from
GCC 5.4 to GCC 6.4 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, c++11-lib, c++11-lang,
c++14-lang, c++0x, c11, or gcc-c++11-lib.
PR: 219275
Fix various compilation issues in python-gammu on Windows.
Improved support for Huawei E3531 and E1756.
Fixed several issues with using library on Windows.
- Convert to USES=localbase
- Patch sample script shebang to reference sh instead of bash
- Fix staging and packaging problems when not using default options
- Add missing dependencies reported by poudriere stage-qa
- Strip installed libraries
N.B. Removal of options oss, sndfile, and portaudio as portaudio and
sndfile is now always needed due to an upstream change.
=Version 4.0.5=
2017-06-19 David Freese <iam_w1hkj@w1hkj.com>
bc29d97: Documentation update
6164c26: TELNET timeout
8922c5d: FD macros
b0928a0: N3FJP PTT
dcca120: Rx/Tx open/close
a49cf18: xmlrpc configuration
36a7fce: FSQ macros
6aaec34: Consistency check fail
7bcd89c: Audio Alerts
5f65d2e: Restore defaults
a9346cd: cw variable squelch
8460fba: INSTALL/README/NEWS
c2c9f38: CW Extended char set
ad8e33e: County field
64b397f: autostart on os x
43b37fe: Rx Context Menu
3aea3ca: Port Audio on Linux
f994b6a: NEWS update
Using ninja instead of make (1) can lead to significant speed ups while building.
Therefore switch from having the ninja generator opt-in to having it opt-out.
Previously cmake-ports that wanted to use ninja could set
CMAKE_NINJA=yes
now, ports that do not work with ninja can set
cmake:<existing args>,noninja
Note, that needing this should be an exception and most often points to a broken
cmake of the port.
The ports using cmake were modified
* removed USES=gmake, if ninja is used
* removed MAKE_ARGS, if ninja is used
* added the cmake-argument noninja if necessary
PR: 219629
PR: 213331
Exp-run by: antoine
Reviewed by: rakuco
Differential Revision: https://reviews.freebsd.org/D10748
