Two new features

Repology links - each port now has a link to repology.org. See issue 148 for details.

Ports I maintain report - port maintainers can now subscribe to a daily report of commits to the ports they maintain. See Watch ports I maintain at Report Subscriptions. Details at issue 138

Search FreshPorts using Google

not searching src

The FreshPorts Search

Include deleted ports

Case sensitive search

Sort by:

Include /src tree

Output format:
HTML
Plain Text

Maximum Effort

Minimal output

Branch:

Notes

Case sensitivity is ignored for "sounds like" and output is ordered by the soundex.

When searching on 'Message ID', the type of match is ignored.

When searching on 'Commit Message' only 'containing' is used.

When searching by 'Under a pathname', your path must start with something like /ports/, /doc/, or /src/. All
commits under that point will be returned. The selected match type is ignored and defaults to 'Starts with'.

Searching for 'sounds like' is only valid for Committer, Maintainer, Package Name, and Port Name.

- pugixml-1.10 conflicts with libSavitar-4.5.0 on
/usr/local/lib/cmake/pugixml/pugixml-config-release.cmake [1]
- I had a TODO in original Makefile to rewrite to use our system pugixml [2]
[1] maciej@pasternacki.net
[2] db
PR: ports/246316

VOLK is a sub-project of GNU Radio. Please see http://libvolk.org for bug
tracking, documentation, source code, and contact information about VOLK.
VOLK is the Vector-Optimized Library of Kernels. It is a library that
contains kernels of hand-written SIMD code for different mathematical
operations. Since each SIMD architecture can be very different and no
compiler has yet come along to handle vectorization properly or highly
efficiently, VOLK approaches the problem differently.
For each architecture or platform that a developer wishes to vectorize for,
a new proto-kernel is added to VOLK. At runtime, VOLK will select the correct
proto-kernel. In this way, the users of VOLK call a kernel for performing
the operation that is platform/architecture agnostic. This allows us to
write portable SIMD code.
Bleeding edge code can be found in our git repository at
https://www.gnuradio.org/git/volk.git/.

I was confused by the jump back in version numbering but got the proper
commit number after the proper 4.5 tag did an unneeded EPOCH bump
(Thinking I was working on CuraEngine) and then managed to leave the
wrong tag 14.5 instead of 4.5 in the version. (Porter Handbook 5.14)
I'll wear the pointy hat.
Mop up the RUN_DEPENDS I missed as noted by lme@ via email.
===
I made it work on my machine but there were a few missing runtime
dependencies:
- cad/cura-engine
- comms/py-serial
- graphics/qt-graphicaleffects
- x11-toolkits/qt-quickcontrols2
After I installed the packages manually Cura starts successfully. :-)
===
Reported by: lme@FreeBSD.org

Updated pkg-descr
The Uranium framework consists of several parts, divided over several modules.
These modules are Core, Backend, Math, Mesh, Scene, Settings and View.
In addition, there are two toolkit-specific modules that implement a lot
of UI bits for the applications.

- Maintainer timeout after 4 months take Maintainership
Reported: 2019-11-26 03:43 UTC by Kyle Evans
Modified: 2020-03-11 21:02 UTC (History)
Total new update to CuraEngine
Cura saw a major rewrite between 15.04 and 4.3.0, hence the need for
PORTEPOCH -- the changeset is too large to enumerate. At a minimum,
the new version solves some issues that users will see attempting to
slice .stl files created from newer Blender versions.
A new port, libArcus, is also included -- this is a prereq for the new
version of Cura and will also be needed for the UI if it's eventually ported.
PR: ports/242242

This is the new, shiny frontend for Cura. Check daid/LegacyCura for the
legacy Cura that everyone knows and loves/hates. We re-worked the
whole GUI code at Ultimaker, because the old code started to become
unmaintainable.
WWW: https://github.com/Ultimaker/Cura/wiki

File metadata and streaming library
As of march 5th the Charon library is the responsibility of the Embedded
Applications team. Pull requests to MASTER have to be verified by the Embedded
Applications team.
WWW: https://github.com/Ultimaker/libCharon

libArcus
This library contains C++ code and Python3 bindings for creating a socket
in a thread and using this socket to send and receive messages based on
the Protocol Buffers library. It is designed to facilitate the communication
between Cura and its backend and similar code.
WWW: https://github.com/Ultimaker/libArcus

Trimesh is a pure Python (2.7-3.4+) library for loading and using triangular
meshes with an emphasis on watertight surfaces. The goal of the library
is to provide a full featured and well tested Trimesh object which allows
for easy manipulation and analysis, in the style of the Polygon object in
the Shapely library.
The API is mostly stable, but this should not be relied on and is not
guaranteed: install a specific version if you plan on deploying something
using trimesh.
WWW: https://pypi.org/project/trimesh/#description

Python-FCL is an (unofficial) Python interface for the Flexible Collision
Library (FCL), an excellent C++ library for performing proximity and
collision queries on pairs of geometric models. Currently, this package
is targeted for FCL 0.5.0.
WWW: https://libraries.io/pypi/python-fcl

This is a snapshot version of FCL at 0.5.0 mainly to support
python-fcl otherwise please use the fcl port.
N.B. python-fcl also needs octomap
FCL is a library for performing three types of proximity queries on a pair of
geometric models composed of triangles.
It performs:
* Collision detection: detecting whether the two models overlap, and optionally,
all of the triangles that overlap.
* Distance computation: computing the minimum distance between a pair of models,
i.e., the distance between the closest pair of points.
* Tolerance verification: determining whether two models are closer or farther
than a tolerance distance.
* Continuous collision detection: detecting whether the two moving models
overlap during the movement, and optionally, the time of contact.
* Contact information: for collision detection and continuous collision
detection, the contact information (including contact normals and contact
points) can be returned optionally.

Every game needs a user interface that matches its look and feel. The purpose
of glooey is to help you make such an interface. Towards this end, glooey
provides 7 powerful placement widgets, a label widget, an image widget,
3 different button widgets, a text entry widget, a variety of scroll boxes
and bars, 4 different dialog box widgets, and a variety of other miscellaneous
widgets. The appearance of any widget can be trivially customized, and
glooey comes with built-in fantasy, puzzle, and 8-bit themes to prove it
(and to help you hit the ground running if your game fits one of those genres).
The philosophy behind glooey is that deriving subclasses from a basic set of
widgets with no default style is the most elegant way to control how
widgets look. This approach is flexible because subclasses can customize or
override most aspects of the basic widgets. But it's also surprisingly
succinct and powerful: specifying a style is usually as simple as setting
a class variable, and styles can be easily composed using either inner
classes or previously defined widgets. This philosophy makes glooey easy
to get started with, and powerful enough to support even the most
complicated games.
WWW: https://pypi.org/project/glooey

This package provides a handful of functions you can use to print debugging
information. There are basically two things that are useful about these
functions. First, they're only one or two letters each, so you can type
them really quickly while debugging. Second, they append the name of the
calling function to whatever you're printing, so you can easily see where
each message came from (and you don't have to hunt down print statements
once you finish debugging).

Properties are a feature in python that allow accessor functions (i.e. getters
and setters) to masquerade as regular attributes. This makes it possible to
provide transparent APIs for classes that need to cache results, lazily load
data, maintain invariants, or react in any other way to attribute access.
Unfortunately, making a property requires an annoying amount of boilerplate
code. There are a few ways to do it, but the most common and most succinct
requires you to decorate two functions (with two different decorators) and
to type the name of the attribute three times:
WWW: https://pypi.org/project/autoprop/

This package provides 2D vector and rectangle classes. These classes were
written to be used in games, so they have some methods that conveniently tie
into pyglet and pygame, but for the most part they are quite general and
could be used for almost anything.
WWW: https://pypi.org/project/vecrec

OpenCTM is a file format, a software library and a tool set for compression
of 3D triangle meshes. The geometry is compressed to a fraction of comparable
file formats (3DS, STL, COLLADA...), and the format is accessible through
a simple, portable API
WWW: https://sourceforge.net/projects/openctm/

Pet portlint regenerate patchfiles while here. [db]
The original one in ports doesn't include readline support . but they
support readline according to the configure. So I think add a readline
support option should be nice
PR: ports/244468
Submitted by: papadavecn@gmail.com

The kitchen sink of Python utility libraries for doing "stuff" in a
functional way. Based on the Lo-Dash Javascript library.
Looking for a library that is more memory efficient and better suited for
large datasets? Check out fnc! It's built around generators and iteration
and has iteratee-first function signatures.
WWW: https://pypi.org/pypi/pydash/

This a simple set of command-line tools that is intended to
be used to decode digital modulations used by ham radio
operators. The main focus is on digital voice modes.
Right now this project enables you to decode DMR and YSF.
PR: ports/244357
Submitted by: vvelox@vvelox.net

Update to 20200107
Also remove all traces of a version number and simplify Makefile.
Not even the About dialog shows a non-date version.
Submitted by: Charlie Li <ml+freebsd@vishwin.info>
Reviewed by: db
Differential Revision: D22986

MFH: r520276
- According to @koobs the dependency on pyephem/ephem is spurious hence removed.
- When gnuradio was first imported into the tree, UHD (Ettus) was pretty much
the only
viable high speed device for it. This is no longer true so default option
removed.
- Noted plist problem with removed UHD corrected.
PR: ports/240546
Reported by: w.schwarzenfeld@utanet.at
Approved by: portmgr (joneum)

- According to @koobs the dependency on pyephem/ephem is spurious hence removed.
- When gnuradio was first imported into the tree, UHD (Ettus) was pretty much
the only
viable high speed device for it. This is no longer true so default option
removed.
- Noted plist problem with removed UHD corrected.
PR: ports/240546
Reported by: w.schwarzenfeld@utanet.at
MFH: 2019Q4

Apologies, I missed this update overnight.
2019-Sep-08: Version 0.6.0
-------------------------------------------------------------------------------
- Bandmap: Perform all screen updates in the main thread (avoid display problems
with Curses which is not thread safe)
- Add "classic" DX cluster mode (linear display of all spots)
- Allow interactive use of the DX cluster (DX cluster menu item)
- Accessibility: Add option (on by default) to show the cursor in the terminal
permanently ("cursoron" in the config file), helping users with screen
readers.

SvxLink release 19.09.1 -- 01 Sep 2019
@sm0svx sm0svx released this 4 days ago
This release of SvxLink have no single big feature addition but a lot of
smaller ones. Some examples are: AFSK metadata transmission for RF linked
remote receivers, per receiver voter delay adjustment, new module ModuleTrx to
remote control transceivers using DTMF, more flexible announcement
configuration and more.
As usual a number of bugs have been fixed. The full list of changes and more
details can be found in the README for release 19.09. Information on
configuration of new features can be found in the manual pages.
Reported by: portscout

Changelog:
## [3.8.0.0] - 2019-08-09
Witness me!
Tonight, we release GNU Radio 3.8.0.0.
It's the first minor release version since more than six years, not without
pride this community stands to face the brightest future SDR on general purpose
hardware ever had.
Since we've not been documenting changes in the shape of a Changelog for the
whole of the development that happened since GNU Radio 3.7.0, I'm afraid that
these release notes will be more of a GLTL;DR (git log too long; didn't read)

Update to 17.12.2
This version supports qt5
SvxLink release 17.12 -- 30 Dec 2017
------------------------------------
The biggest news in this release is the initial revision of the SvxReflector
application. The SvxReflector application is meant to be used as a center point
to link SvxLink nodes together. The new SvxLink ReflectorLogic logic core is
used to connect a SvxLink node to the reflector server. One or more logics can
then be connected to the refelctor using normal logic linking.
In addition a lot of smaller feature additions have been made and also a number
of bugs have been fixed. The full list of changes and more details can be found
below. Information on configuration of new features can be found in the manual
pages.

- update to 2.0.1
- builds on i386 now
- remove MAKE_JOBS_UNSAFE
- Upstream wsjtx build instructions call for their forked
version of hamlib for wsjtx to work correctly.
Upstream distribution includes both wsjtx and a copy of their
forked hamlib with their own build system. This is now used in
this updated port. The cmake build provided does not have an
install/strip target which forces use of do-install.
N.B. If hamlib is already installed, this port will incorrectly
link against the shared library version of hamlib instead of the
private copy provided. There seems no easy solution to this.

What is CubicSDR ?
CubicSDR is the software portion of Software Defined Radio.
By Using hardware that converts RF spectrum into a digital
stream we are able to build complex radios to do many types
of functions in software instead of traditional hardware.
What can I do with CubicSDR ?
Paired with a supported hardware receiver, you can use CubicSDR
to explore the RF world around you. Discover Satellite transmissions,
Amateur Radio, Rail, Areonautical, Shortwave, or any number of
possible signals floating through the air.
WWW: https://cubicsdr.readthedocs.io/en/latest/

Altivec support probably wasn't maintained for years. Fix it to compile
on powerpc64.
Tested also on amd64.
Hardware sponsored by IntegriCloud.
PR: ports/235560
Submitted by: Piotr Kubaj <pkubaj@anongoth.pl>

[ 23:47 db ]splat 1.4.2_1comms Used in calculating path losses, useful to ham radio and others

From submitter:
The current port does not facilitate the installation of splat-hd.
The attached patch resolves that. Also this patch enables having splat-hd
build out with 8x8 tiles.
From db:
- splat-hd was never being built and installed.
- forced HRM build with new option
- cleaned up HRM and pkg-plist
- High resolution 6x6 7x7 and 8x8 need 64bit systems so mark description
but allow foot shooting if user tries high resolution 8x8 on i386
PR: ports/235148
Submitted by: darcy@dbitech.ca