From owner-ports-jp@jp.freebsd.org  Fri Jun 25 11:10:44 1999
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id LAA57151;
	Fri, 25 Jun 1999 11:10:44 +0900 (JST)
	(envelope-from owner-ports-jp@jp.FreeBSD.org)
Received: from dfw-ix10.ix.netcom.com (dfw-ix10.ix.netcom.com [206.214.98.10])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id LAA57146
	for <ports-jp@jp.freebsd.org>; Fri, 25 Jun 1999 11:10:43 +0900 (JST)
	(envelope-from asami@cs.berkeley.edu)
Received: (from smap@localhost)
          by dfw-ix10.ix.netcom.com (8.8.4/8.8.4)
	  id VAA00100; Thu, 24 Jun 1999 21:06:14 -0500 (CDT)
Received: from sji-ca4-28.ix.netcom.com(205.186.212.156) by dfw-ix10.ix.netcom.com via smap (V1.3)
	id rma000057; Thu Jun 24 21:05:44 1999
Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id TAA83100; Thu, 24 Jun 1999 19:05:34 -0700 (PDT)
Date: Thu, 24 Jun 1999 19:05:34 -0700 (PDT)
Message-Id: <199906250205.TAA83100@silvia.hip.berkeley.edu>
X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f
To: me@freebsd.org
CC: garyj@fkr.dec.com, ports@freebsd.org, ports-jp@jp.freebsd.org
In-reply-to: <19990624135208.C1980@consol.de> (message from Michael Elbel on
	Thu, 24 Jun 1999 13:52:10 +0200)
From: asami@freebsd.org (Satoshi - Ports Wraith - Asami)
References:  <19990624135208.C1980@consol.de>
Reply-To: ports-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+990610
X-Sequence: ports-jp 6899
Subject: [ports-jp 6899] Re: cvs commit: ports/editors/xemacs-packages - Imported sources
Errors-To: owner-ports-jp@jp.freebsd.org
Sender: owner-ports-jp@jp.freebsd.org
X-Originator: asami@freebsd.org

 * From: Michael Elbel <Michael.Elbel@consol.de>

 * Hmm, we'd need to have a mule enabled xemacs21 package as well then. You
 * can't use the mule packages without compiling xemacs mule enabled.

Oh.

 * After the creation of separate xemacs-mule ports by Kazuyuki IENAGA I've
 * been wondering if I shouldn't drop mule support in the port
 * altogether. I've kept it so far because it really isn't a lot of work to
 * support it. I'd really like to know if *anybody* is using the stock xemacs
 * port with mule.
 * 
 * All in all, I'd say it isn't worth the hassle to have *two* mule-enabled
 * pre-built packages.

You are quite right.  Actually I was wondering if you two can work to
merge the two ports together.  Is it hard to make it so that
xemacs21/Makefile is capable of building both un-mule and fully
mule-enabled versions (defaulting to the former) and
xemacs21-mule/Makefile will just include it with USE_MULE defined?

 * That's just my opinion, of course. I'll leave the final decision to the
 * ports master.
 * 
 * Michael

Please don't invoke me to make decisions on ports I don't even use
(sorry Ienaga-san, but emacs20 is quite good enough for me ;).

-PW
