X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["597" "Thu" "12" "November" "1998" "09:11:54" "+0000" "Sebastian Rahtz" "s.rahtz@ELSEVIER.CO.UK" nil "18" "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 KAA20553; Thu, 12 Nov 1998 10:34:19 +0100 (MET) Received: from lsv1.listserv.gmd.de (192.88.97.2) by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <11.76CE215C@listserv.gmd.de>; Thu, 12 Nov 1998 10:34:17 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 408570 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Thu, 12 Nov 1998 10:34:11 +0100 Received: from pillar.elsevier.co.uk (root@pillar.elsevier.co.uk [193.131.222.35]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id KAA05845 for ; Thu, 12 Nov 1998 10:34:10 +0100 (MET) Received: from snowdon.elsevier.co.uk [193.131.197.164]; by pillar.elsevier.co.uk (8.8.5/8.8.5) with ESMTP; for ""; sender "s.rahtz@elsevier.co.uk"; id JAA01339; hop 0; Thu, 12 Nov 1998 09:26:06 GMT Received: from srahtz (actually host srahtz.elsevier.co.uk) by snowdon.elsevier.co.uk with SMTP (PP); Thu, 12 Nov 1998 09:33:57 +0000 X-Mailer: emacs 20.3.2 (via feedmail 9-beta-3 Q); VM 6.61 under Emacs 20.3.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <98110912272255@man.ac.uk> <199811101228.MAA14652@nag.co.uk> <13896.14781.711560.872729@srahtz> <19981111162952.B30536@maths.tcd.ie> Message-ID: <13898.42586.749539.995192@srahtz> Reply-To: Mailing list for the LaTeX3 project In-Reply-To: <19981111162952.B30536@maths.tcd.ie> Date: Thu, 12 Nov 1998 09:11:54 +0000 From: Sebastian Rahtz 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: 2877 Timothy Murphy writes: > I wonder if it would not be possible > to lay down a fairly strict protocol > governing "acceptable" packages, > so that one could automate downloading? > very much so. our friend Joachim Schrod was once specifying this, but it never got off the ground. my rules would be: - general applicability ( :-} ) - no duplication of functionality - works with any or all of other packages in collection (within reason) - uses fixed directory structure and file names to allow automated updating - comes with documentation and test file (if possible) Sebastian