X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1076" "Fri" "13" "November" "1998" "08:18:14" "+1000" "Ken Smith" "kgs@MATHS.UQ.EDU.AU" nil "24" "Re: What is \"base\" LaTeX" "^Date:" nil nil "11" nil "What is \"base\" LaTeX" nil nil nil] nil) Received: from listserv.gmd.de (listserv.gmd.de [192.88.97.1]) by mail.Uni-Mainz.DE (8.8.8/8.8.8) with ESMTP id XAA27180; Thu, 12 Nov 1998 23:18:44 +0100 (MET) Received: from lsv1.listserv.gmd.de (192.88.97.2) by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <13.406EEFF5@listserv.gmd.de>; Thu, 12 Nov 1998 23:18:42 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 409412 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Thu, 12 Nov 1998 23:18:37 +0100 Received: from abacus.maths.uq.edu.au (abacus.maths.uq.edu.au [130.102.160.6]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id XAA13920 for ; Thu, 12 Nov 1998 23:18:22 +0100 (MET) Received: from jemima.maths.uq.edu.au (jemima.maths.uq.edu.au [130.102.160.24]) by abacus.maths.uq.edu.au (8.9.0/8.9.0) with ESMTP id IAA07756 for ; Fri, 13 Nov 1998 08:18:14 +1000 (EST) Received: (from kgs@localhost) by jemima.maths.uq.edu.au (8.8.6/0.0.0) id IAA06808 for LATEX-L@URZ.UNI-HEIDELBERG.DE; Fri, 13 Nov 1998 08:18:14 +1000 (EST) Message-ID: <199811122218.IAA06808@jemima.maths.uq.edu.au> Reply-To: Mailing list for the LaTeX3 project Date: Fri, 13 Nov 1998 08:18:14 +1000 From: Ken Smith Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: What is "base" LaTeX Status: R X-Status: X-Keywords: X-UID: 2879 Phillip Helbig wrote on Wed, 11 Nov 1998 17:09:55 GMT (inter alia) > I think the solution is to put more stuff in the core part. One can > actually automatise updating the core quite easily. > Of course, stuff in core must be guaranteed to work with other stuff in > the core etc. On the other hand, it's nice to have contrib stuff `use > at your own risk' at some official (CTAN) site. > To sum up, get rid of contrib/supported. If it's supported, it should ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > go into the core. Perhaps one needs a filter here to avoid redundancy ^^^^^^^^^^^^^^^^ > in the core and assure quality, but basically if it's good, someone has > taken the effort and is supporting it, after this filter why not put it > in the core. There is then core and everything else, which can be like > a trial area. Gradually core can grow. Would someone like to estimate how large this would make the core? I have in mind people installing from scratch on a new machine. Ken Smith kgs@maths.uq.edu.au