Our port of this old window manager is at version 0.0.5, which is
from 2002 (19 years old). At startup, there is a spew of errors
about undefined symbols and the plugins can't be loaded. Clearly,
nobody has been using this.
There is a newer development version 0.0.6 from 2007, but it relies
on Linux-only code.
ok kn@ ajacoutot@
version (the 2.x releases are different enough that the 1.x port isn't
any help if anyone wants to update - newest 2.x release is still 5+
years old), doesn't build with -fno-common, limited hardware support.
audio/clementine may be an alternative; also ipod support could possibly
be added to amarok/banshee/rhythmbox via libgpod if needed.
worth fixing (it's a netstumbler-like toolset for wi(4) - a FreeBSD
forum post from 2009 said "bsd-airtools is dead", and at that point they
already had a newer version than in OpenBSD ports).
"This port combines gcc 3.4.5 from 2005 with a mingw runtime from
2009 or 2010 to target Microsoft Windows." It is woefully obsolete.
If somebody wants to cross-compile from OpenBSD to Microsoft Windows,
they should import a new toolchain.
Noticed because it failed to build with -fno-common.
ok gkoehler@ kn@
other than the usual "python3/<blank>" python version selection and
remove setting MODPY_VERSION=${MODPY_DEFAULT_VERSION_3} again from the
affected ports.
if a port needs 2.x then set MODPY_VERSION=${MODPY_DEFAULT_VERSION_2}.
This commit doesn't change any versions currently used; it may be that
some ports have MODPY_DEFAULT_VERSION_2 but don't require it, those
should be cleaned up in the course of updating ports where possible.
Python module ports providing py3-* packages should still use
FLAVOR=python3 so that we don't have a mixture of dependencies some
using ${MODPY_FLAVOR} and others not.
Fails with "-fno-common" and upstream HOMEPAGE (equals MASTER_SITES) now
points to https://9fans.github.io/plan9port/unix/ which provides
unversioned tarballs with links to checksums that yield 404; same story
for their manual page links on that page. The GitHub repository does
not contain releases either.
This is now unportable but there is an up-to-date plan9/plan9port which
packages from the very same upstream (using git commit hashes and dates as
versions) which ships also ships mk(1).
OK sthen
We package 0.8.3 05-Apr-2012 but 0.8.4 in 13-Jul-2013 and 0.8.5 in
08-Oct-2018 were released; the release tarball's NEWS file states
"changes to make it compile with newer g++ and libcrypto" and
"Manually parse /etc/resolv.conf, rather than attempting to make use of the
res data structure (which at least on OpenBSD no longer actually contains
the addresses of resolvers)".
This port fails to build with "-fno-common" and noone has spoken up on
ports@ to fix and update it.
PS: http://www.mailavenger.org/NEWS is sitll missing 0.8.5 changes, so
best look at the actual tarball.
OK gnezdo
Fails to build with "-fno-common" and busy loop stat(2)s watched files
driving up CPU usage instead of using kevent(2) or so.
No activity upstream, FreeBSD maintains a port with local patches called
(security/l0pht-watch in their ports tree) in case anyone is interested
in resurrecting this.
OK jca naddy
Uses a bootstrap.py developed upstream to limit Haskell dependencies
to just lang/ghc. This will allow cabal-install to be at the base of
cabal-based Haskell ports framework.
Looks fine by kili@
