Date: Tue, 18 Feb 1997 23:24:42 +0900 From: Makoto MATSUSHITA <matusita@ics.es.osaka-u.ac.jp> To: FreeBSD-gnats-submit@freebsd.org Subject: ports/2760: New ports, jp-fvwm-2.0.45 Message-ID: <19970218232442A.matusita@ics.es.osaka-u.ac.jp> Resent-Message-ID: <199702181430.GAA06656@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 2760 >Category: ports >Synopsis: New ports, jp-fvwm-2.0.45 >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Tue Feb 18 06:30:02 PST 1997 >Last-Modified: >Originator: Makoto MATSUSHITA >Organization: Osaka University / Japan FreeBSD Users' Group >Release: FreeBSD 2.2-RELEASE i386 >Environment: Tested on FreeBSD 3.0-CURRENT and FreeBSD 2.2-ALPHA. >Description: This is an internationalized fvwm. I'm the also the maintainer of fvwm internationalization patch. This ports was named 'jp-fvwm', but its capability is only depended on X locale model, so if you wish, displaying chinese, korean, russian, will do. I think 'i18n-fvwm' or whatever name is more appliciated, but no ports uses 'i18n-' prefix, so I decided to use 'jp-' instead. This ports cannot co-exists x11/fvwm or x11/fvwm2, because its binary name is 'fvwm' or 'fvwm2'. jp-fvwm-2.0.45 uses 'fvwm2' as fvwm binary name, but 'make FVWMNAME=fvwm' makes 'fvwm' as fvwm binary name. Well, libxpg4-related problem is exists, between FreeBSD-2.2 or later and FreeBSD 2.1.6-RELEASE or before. This port considers libxpg4 is available or not:) It should be considered as XFree86 problem but... >How-To-Repeat: >Fix: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970218232442A.matusita>