X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1753" "Wed" "11" "November" "1998" "17:09:55" "GMT" "Phillip Helbig" "helbig@MAN.AC.UK" nil "41" "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 SAA10057; Wed, 11 Nov 1998 18:13:30 +0100 (MET) Received: from lsv1.listserv.gmd.de (192.88.97.2) by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <8.71AD7CD2@listserv.gmd.de>; Wed, 11 Nov 1998 18:13:28 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 407953 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Wed, 11 Nov 1998 18:13:23 +0100 Received: from multivac (multivac.jb.man.ac.uk [130.88.24.128]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with SMTP id SAA28832 for ; Wed, 11 Nov 1998 18:13:21 +0100 (MET) X-VMS-To: SMTP%"LATEX-L@urz.uni-heidelberg.de" X-VMS-Cc: HELBIG Message-ID: <98111117095539@man.ac.uk> Reply-To: Mailing list for the LaTeX3 project Date: Wed, 11 Nov 1998 17:09:55 GMT From: Phillip Helbig 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: 2862 > > I cannot speak for the others, but i would very much welcome an agreed > > "recommended" level of packages above the base level, so that one can > > stop saying to people "oh, sorry, you have XXXtex, they dont ship > > package ZZZ" Yes, this is the problem. > I wonder if it would not be possible > to lay down a fairly strict protocol > governing "acceptable" packages, > so that one could automate downloading? > > At present one actually has to read the README > to find out what to do > (eg put associated font files in the right place). Right. A pain. 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. -- Phillip Helbig Email ......... p.helbig@jb.man.ac.uk Nuffield Radio Astronomy Laboratories Tel. .... +44 1477 571 321 (ext. 297) Jodrell Bank Fax ................ +44 1477 571 618 Macclesfield Telex ................ 36149 JODREL G UK-Cheshire SK11 9DL Web ... http://www.jb.man.ac.uk/~pjh/ My opinions are not necessarily those of NRAL or the University of Manchester.