From xemacs-m  Fri Apr 18 09:59:55 1997
Received: from mgate.uni-hannover.de (mgate.uni-hannover.de [130.75.2.3])
	by xemacs.org (8.8.5/8.8.5) with SMTP id JAA28344
	for <xemacs-beta@xemacs.org>; Fri, 18 Apr 1997 09:59:54 -0500 (CDT)
Received: from helios (actually helios.tnt.uni-hannover.de) by mgate 
          with SMTP (PP); Fri, 18 Apr 1997 16:59:41 +0200
Received: from daedalus.tnt.uni-hannover.de by helios (SMI-8.6/SMI-SVR4) 
          id QAA10008; Fri, 18 Apr 1997 16:59:08 +0200
Received: by daedalus.tnt.uni-hannover.de (SMI-8.6/SMI-SVR4) id QAA00608;
          Fri, 18 Apr 1997 16:59:03 +0200
Date: Fri, 18 Apr 1997 16:59:03 +0200
Message-Id: <199704181459.QAA00608@daedalus.tnt.uni-hannover.de>
From: Heiko Muenkel <muenkel@tnt.uni-hannover.de>
To: hniksic@srce.hr
Cc: xemacs-beta@xemacs.org
Subject: Re: Packaging criteria
In-Reply-To: <kigenc8r1z9.fsf@jagor.srce.hr>
References: <m2ohbdz4ey.fsf@altair.xemacs.org> <kign2qxouar.fsf@jagor.srce.hr> <m2d8rs6dgd.fsf@altair.xemacs.org> <kigiv1kok6z.fsf@jagor.srce.hr> <m24td468p4.fsf@altair.xemacs.org> <kigenc8r1z9.fsf@jagor.srce.hr>
X-Mailer: VM 6.22 under 19.15 XEmacs Lucid
X-Face: n}R'l6CHRf>pi&bj7[x0CW3:kmXm@1)7m+l*9[fp;-Ow4Xe~=5E;skf?2> 
        y]f{HzB|Q(\V9+y$PP~.4G[2n4W7{6Ilm[AMY9B:0kj.K_$-d%p4YIF*bX;=ADp6{ 
        HS@NEv9c.VII+9PgXHASx}K(jy^t=q%qzZ72q1e4E;O!$A$`&wgtLk"1%p.nC_G!] 
        4d1!+J4Q#YD_iXeEy`1x)d\r$1Qn\'23n|[8Y_xzuXJJ7W(EGqnzB]`]aq??;+z=) 
        DW~\'Vq&F'g%QU[Mv2:}nS>SdZFTEC2GsgB=Q,:~H<R5S[:ZN%B:s0;|v1x"Jb
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII

>>>>> "Hrv" == Hrvoje Niksic <hniksic@srce.hr> writes:

    Hrv> Steven L Baur <steve@miranova.com> writes:
    Hrv> Yes, but editing C code is the most basic functionality
    Hrv> XEmacs can possibly provide to Unix programmers.  If we
    Hrv> decline to provide cc-mode, it will mean openly agree that
    Hrv> the core is unusable rather than Spartan.

C, C what's C? :-)

    Hrv> Personally, I've asked a number of people what they think
    Hrv> about that, and all of them agree that cc-mode must remain
    Hrv> shipped with the XEmacs core.

    Hrv> Please, think well and hard before removing cc-mode.  If you
    Hrv> decide that way, then I'll have to ask for the old c-mode to
    Hrv> be included.  That would really be ridiculous, but so be it.
    Hrv> I'll fight for XEmacs to include at least one C mode in even
    Hrv> the most Spartan configuration.  I'd like it to be the best
    Hrv> one -- cc-mode.

I think, that the core XEmacs should only contain packages, which are
necessary to start up an XEmacs and maybe to get and install the rest
of the packages. The smaller the better. But we should also provide
tar files with all packages.

In my mind removing a package from the core system doesn't mean to
remove it from the XEmacs distribution - and we should keep up
testing these packages.

I think it would be nice to spilt the distribution in the following
parts:

xemacs-20.xx.tar.gz: the same as now, the whole XEmacs sources with
	all packages; there should configure or install options
	to build different sized installations

xemacs-20.xx-<architecture>.tar.gz: the same as now?

xemacs-20.xx-packages-necessary.tar.gz: the necessary packages to
	start the XEmacs - nothing more, nothing less;

xemacs-20.xx-packages-install.tar.gz: packages, necessary to get
	and install further packages from ftp.xemacs.org; this 
	should also contain descriptions (at least something like
	the LSM files for Linux packages) of all available 
	packages, so that's easier for a user to find a package;

xemacs-20.xx-packages-rest.tar.gz: the rest of all the
	packages, maintained or tested by the XEmacs beta testers.


Heiko

PS: The fundamental mode is sufficient to edit every file in every
    language and there are sometimes situations where users would
    prefer or even need such a spartanic XEmacs. 
    

