Window Maker is an X11 window manager designed to give additional
integration support to the GNUstep Desktop Environment. In every
way possible, it reproduces the elegant look and feel of the
NeXTstep[tm] GUI. It is fast, feature rich, easy to configure, and
easy to use. In addition, Window Maker works with GNOME and KDE,
making it one of the most useful and universal window managers
available.
===> The following configuration options are available for windowmaker-0.96.0_5:
DOCS=on: Build and/or install documentation
IMAGEMAGICK=on: ImageMagick image processing support
NLS=on: Native Language Support
===> Use 'make config' to modify these settings
Bump portrevision due to upgrade of devel/gettext.
The affected ports are the ones with gettext as a run-dependency
according to ports/INDEX-7 (5007 of them) and the ones with USE_GETTEXT
in Makefile (29 of them).
PR: ports/124340
Submitted by: edwin@
Approved by: portmgr (pav)
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.
For the ports that I maintain, do the following as appropriate:
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.
1. Move the include of bsd.port.pre.mk before OPTIONS based on a recent
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)
Patch to fix a debilitating problem for amd64 users. To quote Scott:
"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)
Update to 0.91.0, the latest version from the window maker team.
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
(Only the first 15 lines of the commit message are shown above )
- Fix build on 4-stable
- 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>
Update to 0.90.0, the latest release from the Window Maker team.
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
In preparation for 0.90.0, delete all patches that involve charset
manipulation and zh_TW.Big5. The new charset is UTF-8 everywhere,
and zh_TW is now built into the distribution.
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.
Let be hohest: I really don't have a time now to properly maintain all
these great pieces of software, so that let others with more free time
to take over them.
gettext upgrade uber-patch (stage 3)
- switch devel/gettext (0.11.1) on, installing full package
- flip devel/gettext-old (0.10.35) to installing only static binaries
with a "-old" suffix -- gettext-old will have its deorbit burn
sequence initiated just after 4.6-RELEASE
- fix up ports for the new world order
Reviewed by: portmgr
Use ${ECHO_CMD} instead of ${ECHO} where you mean the echo command; the ECHO
macro is set to "echo" by default, but it is set to "true" if make(1) is
invoked with the -s option while ECHO_CMD is always set to the echo command.
1. Backport two patches from windowmaker-i18n port; 2. add wmicons into
RUN_DEPENDS and remove similar functionality from this port; 3. due to
(1) bump PORTREVISION.
Explicitly require ${LOCALBASE}/lib/libfreetype to be present at the build time,
because WM may fail to build if XFree86-4's version of libfreetype.so.6 is
detected and freetype2 port is not installed (XFree86 doesn't install any
freetype's header files). This is temporarly workaround until jmz will fix
XFree86-4 properly.
(1) Add new variable, XFREE86_VERSION, to specify which version of XFree86
(3 or 4) to depend to when USE_XLIB is set. XFREE86_VERSION defaults to 3
for now, but adventurous users can override it in /etc/make.conf. When
XFREE86_VERSION=3, USE_XLIB will add a dependency to x11/XFree86; when it
is set to 4, the dependency will be to x11/XFree86-4-libraries. When
XFREE86_VERSION=4, the PKG_IGNORE_DEPENDS and ALWAYS_BUILD_DEPENDS hacks
to avoid messing with XFree86 are turned off.
Fix MASSIVE typo INSTALL_SHLIBS --> INSTALLS_SHLIBS, which occured because I
just cun'n'pasted the name from Satoshi's commit message without checking it.
