This project uses rump kernels to provide the Rumprun unikernel.
Rumprun works on both hypervisors (eg. KVM and Xen) and bare metal.
Rumprun can be used with or without a POSIX'y interface, and supports
applications written in (but not limited to):
C, C++, Erlang, Go, Java, Javascript (node.js), Python, Ruby and Rust.
PR: 225117
Submitted by: Fabian Freyer <fabian.freyer@physik.tu-berlin.de>
Reviewed by: yuri
Sponsored by: Netzkommune GmbH
Differential Revision: https://reviews.freebsd.org/D13888
Database of IDs used in Plug and Play devices. This file is taken
from the hwdata package (https://github.com/vcrhonek/hwdata), because
the offical upstream (http://uefi.org/pnp_id_list) does not have a
easy to use file.
Submitted by: Ting-Wei Lan <lantw44@gmail.com>
lxi-tools is a collection of open source software tools that enables control
of LXI compatible instruments such as modern oscilloscopes, power supplies,
spectrum analyzers etc.
All features are consolidated in the 'lxi' application which provides a
simple commandline interface to discover LXI instruments, send SCPI
commands, and capture screenshots from supported LXI instruments.
lxi-tools rely on liblxi for all communication.
WWW: https://lxi-tools.github.io/
PR: 224714, D13686
Submitted by: Dmitri Goutnik <dg@syrec.org>
liblxi is an open source software library which offers a simple API for
communicating with LXI compatible instruments. The API allows applications
to discover instruments on your network, send SCPI commands, and receive
responses.
WWW: https://lxi-tools.github.io
PR: 224713, D13685
Submitted by: Dmitri Goutnik <dg@syrec.org>
This took quite a lot of time because Qt's own build system underwent
several changes in 5.8.0 that took a while to adapt to.
And, of course, qt5-webengine is a behemoth that we need to patch like crazy
due to its bundling of Chromium. In fact, most of the Chromium patches in
qt5-webengine have been imported with no changes from www/chromium@433510
("www/chromium: update to 56.0.2924.87").
New port: accessibility/qt5-speech
Bigger changes to Qt5 ports we had to make:
- Qt now allows using a configure.json file to define configuration options
and specify configuration checks that can be done when qmake is invoked.
However, configure.json checks done in a subdirectory only propagates to
subdirectories, and checks elsewhere will fail if all .pro files are being
parsed at once (i.e. qmake -recursive), so several ports had to switch to
USES=qmake:norecursive along with manual additional qmake invocations in
subdirectories in order to work. It's been mentioned in a few places such
as Qt's bug tracker that qmake's recursive mode is pretty much deprecated,
so we might switch to non-recursive mode by default in the future.
- Uses/qmake.mk: Introduce QMAKE_CONFIGURE_ARGS. qmake now accepts
arbitrary options such as '-foo' and '-no-bar' at the end of the
command-line. They can be specified in QMAKE_CONFIGURE_ARGS.
- graphics/qt5-wayland: The port can only be built if graphics/mesa-libs is
built with the WAYLAND option, so a corresponding option (off by default)
was added to the port.
- misc/qt5-doc: Switch to a pre-built documentation tarball. The existing
port was not working with Qt 5.9. Instead of trying to fix it, switch to
what Gentoo does and fetch a tarball that already contains all
documentation so that we do not have to build anything at all. The
tarball's name and location in download.qt.io look a bit weird, but it
seems to work fine.
- www/qt5-webengine: Use binutils from ports, Chromium's GN build system
generates a build.ninja that uses ar(1) with the @file syntax that is not
supported by BSD ar, so we need to use GNU ar from binutils.
- x11-toolkits/qt5-declarative-render2d: This port was merged into the main
Qt Declarative repository upstream, and into x11-toolkits/qt5-quick in the
ports tree.
Changes to other ports we had to make:
- biology/ugene: Drop a '#define point "."' that is not present in more
recent versions of the port. Defining a macro with such a common name
causes build issues with Qt 5.9, which uses |point| as an argument name in
methods.
- cad/qelectrotech: Fix plist with Qt 5.9. Directories are no longer
installed with `cp -f -R', but rather `qmake install qinstall', which does
not install
%%DATADIR%%/elements/10_electric/20_manufacturers_articles/bosch_rexroth/.directory
That's a local file that should not even have been part of the tarball
anyway.
- chinese/gcin-qt5: Add additional private Qt directories (which should not
be used in the first place) to get the port to build with Qt 5.9.
- devel/qtcreator: Fix plist with Qt 5.9. Something changed in qdoc and some
test classes no longer generate documentation files.
- security/keepassx-devel: Import a patch sent upstream almost a year ago to
fix the build with Qt 5.9.
Thanks to antoine for the exp-run, and tcberner and Laurent Cimon
<laurent@nuxi.ca> for landing changes in our qt-5.9 branch.
PR: 224849
Thefuck is a magnificent app which corrects your previous console command.
It tries to match a rule for the previous command, creates a new command
using the matched rule and runs it. Thefuck comes with a lot of predefined
rules, but you can create your own rules as well.
WWW: https://github.com/nvbn/thefuck
PR: 224263
Approved by: adamw
Differential Revision: https://reviews.freebsd.org/D13460
In this case, we dropped a runtime dependency, so it is possible the package
could have been created before and just failed at installation time.
PR: 224870
Upstream no longer ships the contents of misc/py-qt5-doc, so the port has been
removed.
This is also a requirement for updating the Qt5 ports, as the PyQt5 version
currently in the tree has license conflicts with later Qt versions.
Big thanks to tcberner for doing most of the work here, and antoine for the
exp-run.
PR: 224739
Note: Unfortunately this does not fix this issue on the FreeBSD console.
PR: 217758
Submitted by: Alexander Moisseev <moiseev@mezonplus.ru>
Reported by: Dron <dron_2@ua.fm>
Reported by: danfe
MFH: 2017Q4
from absolute links to relative links.
Bump PORTREVISION since this does affect the resulting package in a
material manner.
PR: 224230
Reported by: wosch
We were not setting the flag to select the GNUstep ABI, so were defaulting to
using the GCC-compatible version, which was likely to trigger a lot of subtle
bugs. This was noticed when C++ exceptions thrown through Objective-C stack
frames caused segfaults.
- 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
