OpenZz is a dynamic parser which allows its grammar to be extended by
commands written in its own Zz language. Due to the interpreted and
dynamic nature of the parser OpenZz can be used to develop both fast
language prototypes and full compilers.
WWW: http://openzz.sourceforge.net/
Remove expired ports:
2021-04-01 ftp/wzdftpd: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
2021-04-01 astro/roadmap: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
2021-04-01 games/cosmo: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
2021-04-01 games/bomberinstinct: Unmaintained and dead upstream, does not build
with -fno-common (llvm 11)
2021-04-01 games/drm: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
2021-04-01 games/bygfoot: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
2021-04-01 games/cre: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
2021-04-01 irc/hybserv: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
2021-04-01 irc/xaric: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
2021-04-01 mail/elmo: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
2021-04-01 misc/cave: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
2021-04-01 security/bugs: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
2021-04-01 security/dmitry: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
(Only the first 15 lines of the commit message are shown above )
Extend expiration of ports broken with -fno-common
Extend the expiration of unmaintained leaf ports that are broken with
-fno-common and previously had a short expiration date. The new date is set
to 2021-04-01, meaning the ports will be in the 2021Q2 branch, giving people
until 2021-06-30 (10 months from now) to fix issues.
Improve the wording of the deprecation message, mentioning both llvm 11 and
-fno-common.
Bump portrevision to force reinstall. This way the warning message about
deprecation will be displayed to users installing or reinstalling the
software.
MFH: 2020Q3 (maybe)
Cleanup DIST* variables.
When appropriate:
- Try to use DISTVERSION{SUF,PRE}FIX
- Replace PORTNAME-PORTVERSION by DISTNAME
- Convert MASTER_SITES to use macros
- Other light cleanup
With hat: portmgr
Sponsored by: Absolight
-Repocopy devel/libtool15 -> libtool22 and libltdl15 -> libltdl22.
-Update libtool and libltdl to 2.2.6a.
-Remove devel/libtool15 and devel/libltdl15.
-Fix ports build with libtool22/libltdl22.
-Bump ports that depend on libltdl22 due to shared library version change.
-Explain what to do update in the UPDATING.
It has been tested with GNOME2, XFCE4, KDE3, KDE4 and other many wm/desktop
and applications in the runtime.
With help: marcus and kwm
Pointyhat-exp: a few times by pav
Tested by: pgollucci, "Romain Tartière" <romain@blogreen.org>, and
a few MarcusCom CVS users. Also, I might have missed a few.
Repocopy by: marcus
Approved by: portmgr
Mass-conversion to the USE_AUTOTOOLS New World Order. The code present
in bsd.autotools.mk essentially makes this a no-op given that all the
old variables set a USE_AUTOTOOLS_COMPAT variable, which is parsed in
exactly the same way as USE_AUTOTOOLS itself.
Moreover, USE_AUTOTOOLS has already been extensively tested by the GNOME
team -- all GNOME 2.12.x ports use it.
Preliminary documentation can be found at:
http://people.FreeBSD.org/~ade/autotools.txt
which is in the process of being SGMLized before introduction into the
Porters Handbook.
Light blue touch-paper. Run.
Apply a big libtool patch to allow porters to use the libtool installed by
the libtoolX ports instead of the one included with each port. Ports that
set USE_LIBTOOL_VER=X will now use the ports version of libtool instead of
the included version. To restore previous behavior, use the new macro,
USE_INC_LIBTOOL_VER. Both macros accept the same argument: a libtool version.
For example, to use the ports version of libtool-1.5, add the following to
your Makefile:
USE_LIBTOOL_VER= 15
To use the included version of libtool with extra hacks provided by
libtool-1.5, add the following to your Makefile:
USE_INC_LIBTOOL_VER= 15
With this change, ports that had to add additional libtool hacks to prevent
.la files from being installed or to fix certain threading issues can now
delete those hacks (after appropriate testing, of course).
PR: 63944
Based on work by:eik and marcus
Approved by: ade (autotools maintainer)
Tested by: kris on pointyhat
Bound to be hidden problems: You bet
Whoa there, boy, that's a mighty big commit y'all have there...
Begin autotools sanitization sequence by requiring ports to explicitly
specify which version of {libtool,autoconf,automake} they need, erasing
the concept of a "system default".
For ports-in-waiting:
USE_LIBTOOL=YES -> USE_LIBTOOL_VER=13
USE_AUTOCONF=YES -> USE_AUTOCONF_VER=213
USE_AUTOMAKE=YES -> USE_AUTOMAKE_VER=14
Ports attempting to use the old style system after June 1st 2004 will be
sorely disappointed.
