Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3CF7A23E.7070003@ece.gatech.edu>
Date: Fri, 31 May 2002 12:18:06 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
CC: "'Jan Nieuwenhuizen'" <janneke AT gnu DOT org>, cygwin AT cygwin DOT com
Subject: XEmacs on cygwin [Was: Re: missing file FOO.dll]
References: <000701c208bc$c3346560$0200a8c0 AT lifelesswks>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Robert Collins wrote:

 
> XEmacs uses a fork of setup. Someone who cares might like to suggest
> that they update their fork to a more recent codebase, or ... provide a
> setup.ini for cygwin users.


Well, their fork of setup does more than just unpack the packages.  It 
also mucks with the registry, sets up shortcuts, etc.  (I know, our 
setup does those things too).

Now, if the grand "data-driven" scheme is complete, THEN
   a) if XEmacs updates their setup.exe to the recent codebase AND
   b) they create a "package" that handles those items (but it can't 
rely on cygwin tools to do its magic, because they uuse the same 
setup.exe to install the purely native XEmacs; the end user might not 
have any cygwin tools installed)
   c) we figure out how to handle the relocation problem (*)

(*) We pick a cygwin root, and install everything under that -- but the 
packages must follow certain guildlines: /usr, /etc, etc.  They pick an 
XEmacs root and install everything under that -- and have few 
guidelines.  Currently, the XEmacs tarballs themselves are packaged as:
   bin/i686-pc-cygwin/
   lib/xemacs-21.4.6/
   man/
But the lisp packages are packaged as
   pkginfo/
   lisp/
   lib-src/
   etc/
   info/
   man/
And xemacs' setup "knows" to unpack those under
   <xemacs root>/xemacs-packages/
Just like our setup "knows" to unpack -src tarballs under
   <cygwin root>/usr/src

To sum up: this harmonization won't be easy -- even if the XEmacs folks 
are inclined to do so, which I doubt.

--Chuck



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/