From: alias-disabled-received@ieee.org (IEEE Member Alias Disabled)
Date: Mon, 6 Oct 2003 07:21:40 -0400 (EDT)
We apologize! The IEEE Personal Email Alias you trying to reach was disabled.
who did not respond to my email confirming whether they have an active
interest in maintaining the port:
sue reg rv jmb dima reg horikawa msmith jhs ue
Long long time ago, my friend Mr. yamamoto made an I18N_MB patch. It
was used mainly in Japan since it enable fvwm to display Japanese characters
in the menu, titlebar, and so on. However, and unfortunately, it was
not included original fvwm code at that time since less people need it.
Since then, I maintained the I18N_MB patch to adopt new fvwm releases.
IIRC, this patch is based on the hack for TWM (see X11R5 contrib), and
influences to other fvwm-derived window managers to be i18n-ed (e.g.,
afterstep, windowmaker, etc.)
Soon after the fvwm development team was re-organized as current form, I
tried pushing I18N_MB patch to be included to original fvwm code. It was
great pleasure for me but I have no time to test it; my desktop environment
is tainted with Windows, and I'm lazy to update my fvwm, that runs on VMware.
Recently, I've heard from kris that this ports is broken on 5-current and
sparc64 environment. It seems that it comes from header misuse or something
like that. Maybe I can fix it, but I don't do that. I would be good
chanse to kill this ports, and use the original fvwm code which is already
included this patch for a long time. I believe that fvwm code is still
well-maintained, it should work as expected; I've heard from many people
that it works, and I've just confirmed that. There's no reason to switch it.
Anyway, standalone I18N_MB patch is now dead from FreeBSD ports. Thanks
to the original author yamamoto (he's maybe workin' at panasonic.com but
I don't know how to contact him,) subscribers of fvwm-users-jp mailinglist
(note: it was concluded already,) people who send me a comment/patch, and
ports/x11-wm/fvwm2-i18n users.
PS: I intentionally give a little bit funny PKGNAMESUFFIX to this ports,
to keep this package name unchanged. It should be changed further releases.
Committed at: Executive floor lounge, Hilton Anaheim.
gettext and add it to LIB_DEPENDS.). [1]
- INSTALLS_SHLIB added to the Makefile (Only in case a library
get installed by the port.)
- remove NO_FILTER_SHLIB
- Replaced GNU_CONFIGURE with USE_LIBTOOL if INSTALLS_SHLIB was
set in the Makefile
- bump PORTREVISION
Noted By: Dinesh Nadarajah <dinesh_list@sbcglobal.net> [1]
Waimea by default uses Esetroot to set the background image.
However this executable is part of the eterm-port; thus
waimea should list eterm as a dependancy.
Informed maintainer
PR: ports/50628
Submitted by: Alex Kiesel <kiesel@schlund.de>
Fluxspace provides a framework and modules for adding
event-driven behavior to Fluxbox as an external component.
A variety of features and enhancements can be introduced
more easily without modifying Fluxbox's C++ code.
WWW: http://www.isomedia.com/homes/stevencooper/projects/fluxspace.html
PR: ports/50405
Submitted by: Eirik Nygaard <eirikn@bluezone.no>
patch involved patching the core auto* routines in KDE to accept the
PTHREAD_* variables in the environment, with fallbacks. We decided the
easiest way to implement this in ports was to generate configure instead
of risking incorrect generation at port configure time.
Said patch has already been committed to HEAD in KDE and as such will be
removed with the 3.2 upgrade once it is released.
Ports using Makefile.kde that shouldn't be using them (i.e. non-KDE
modules) have this support commented out due to lack of patch.
Helped out: Adriaan de Groot <adridg@cs.kun.nl>
Lauri Watts <lauri@kde.org>
Andy Fawcett <andy@athame.co.uk>
