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.
1. Add myself as a backup master site (Sourceforge and CPAN ports
already have good enough coverage, so skip them).
2. For all ports that have them, download the PGP signature files.
3. For ports in 2, add a verify target to the Makefile
4. For ports where I was already providing a master site, update the URL.
5. Pet portlint in a couple of places.
post to -ports on this topic
2. Fix build on amd64 by not trying to inline asm code designed for i386
3. Add a patch to fix window positioning on amd64, from
http://article.gmane.org/gmane.compw.window-managers.windowmaker.devel/749
2 and 3 provided/reminded by Dejan Lesjak <dejan.lesjak@ijs.si>
Fixes for 2 and 3 tested by Dejan, and A Dude <adudek16@gmail.com>.
Approved by: portmgr (krion)
"While it compiles and seems to start fine, it will crash if you
start any GTK-based program, including Firefox and Mozilla ...
GTK populates the NET_WM_ICON X11 property with incorrectly padded
data, and WindowMaker blindly reads it out and winds up passing
garbage to some X libraries, which in turn abort the entire process ...
Fortunately, handling this X11 property is not mandatory as there are
other more reliable ways to pass icon state through X (and in fact very
very few other window managers even try this), so it's safe to avoid the
whole mess by stubbing it out and letting Windowmaker fall back to a
more reliable method."
I've tested this patch with i386 windowmaker, and haven't noticed any
differences. I have xterms and various other things doing fancy stuff
with window and icon titles, so I'm pretty confident that this will
be safe for users of all ARCH's. It's also possible that it will help
those users who were having weird QT problems, but I was not able to
reproduce that problem so I can't say for sure.
Submitted by: scottl
Approved by: portmgr (krion)
It contains several bug fixes, especially for the new alt-tab code.
1. Adopt this port, at least for the time being. I use it every day,
and follow the wm-user list so I'm probably qualified.
2. Update the descriptions of the OPTIONS.
3. Restore the knob for KDE, and add knobs for XINERAMA and the
additional LINGUAS files. These, and the XKB_STATUS knobs are all
off by default, but on for the PACKAGE_BUILDING case. I borrowed
this concept from the fluxbox port.
4. Add a knob for the experimental virtual desktop code, off by default.
The window maker folks warn that this is still experimental, so users
shouldn't wander into it by mistake.
5. Instead of bumping the SHLIB version number to 5, set it back to 4.
The window maker folks use N.N.N for their libwraster version string,
and their version for the 0.80.2 version of window maker was 2.3.0.
Thus, our previous version number of 4 was already bogus, so keep it
bogus even though they've bumped their version to 3.N.N. The new lib
is forward compatible for apps compiled with old library (I've tested
many of them), and this "fixes" all the ports that depend on libwraster.
6. Make the locale files hidden under the LINGUAS knob conditional
in the plist.
- Fix libwraster shared library version
- Remove a patch which is no longer needed
- Remove options which are no longer supported
- Fix pkg-plist
- Revise pkg-descr
PR: ports/73082
Submitted by: KATO Tsuguru <tkato432@yahoo.com>
This release adds many new features, including font anti-aliasing.
1. Update LIB_DEPENDS to include Xft
2. Modernize USE_LIBTOOL
3. Hermes is no longer relevant
4. Update man page list and pkg-plist for new version
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
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.
