X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1409" "Thu" "16" "November" "1995" "13:21:00" "GMT" "Frank Bennett" "fbennett@RUMPLE.SOAS.AC.UK" nil "37" "Re: distribution conditions on packages and other LaTeX software" "^Date:" nil nil "11" nil nil nil nil] nil) Received: from listserv.gmd.de (listserv.gmd.de [192.88.97.1]) by trudi.zdv.Uni-Mainz.DE (8.6.12/8.6.12) with ESMTP id PAA09624 for ; Thu, 16 Nov 1995 15:13:38 +0100 Received: from listserv.gmd.de by listserv.gmd.de (LSMTP for OpenVMS v1.0a) with SMTP id B1199852 ; Thu, 16 Nov 1995 15:00:12 +0100 Received: from VM.URZ.UNI-HEIDELBERG.DE by VM.URZ.UNI-HEIDELBERG.DE (LISTSERV release 1.8b) with NJE id 1493 for LATEX-L@VM.URZ.UNI-HEIDELBERG.DE; Thu, 16 Nov 1995 13:25:38 +0000 Received: from DHDURZ1 (NJE origin SMTP@DHDURZ1) by VM.URZ.UNI-HEIDELBERG.DE (LMail V1.2a/1.8a) with BSMTP id 8205; Thu, 16 Nov 1995 13:23:55 +0000 Received: from rumple.soas.ac.uk by vm.urz.Uni-Heidelberg.de (IBM VM SMTP V2R2) with TCP; Thu, 16 Nov 95 13:23:52 CET Received: by rumple.soas.ac.uk (Smail3.1.29.1 #3) id m0tG4Ff-0006OuC; Thu, 16 Nov 95 13:21 GMT Message-ID: Reply-To: Mailing list for the LaTeX3 project In-Reply-To: <199511151659.LAA01214@aleph.bu.edu> (message from Matthew Swift on Wed, 15 Nov 1995 11:59:54 -0500) Date: Thu, 16 Nov 1995 13:21:00 GMT From: Frank Bennett Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: distribution conditions on packages and other LaTeX software Status: R X-Status: X-Keywords: X-UID: 1708 I would like to know how to release a package (class, script, etc.) with distribution conditions most preferable to the LaTeX3 team. The best would be something written out that I could simply cut and paste, making the necessary substitutions for names and so on. This is a really good idea. It does worry me a little that the stuff I've written to support LaTeX3 might be affirmatively ignored by the core team because I've put license conditions on it that are reminiscent of the GPL in some consequential way. [ ... ] 1) a literate source (e.g., .dtx or noweb source) 2) a code file extracted from (1) (e.g., a .sty file, a shell script) 3) a documentation file extracted from (1) (probably a .dvi file) 4) a standalone file (a style file, shell script, documentation file) 5) a configuration file, which may be modified by the user 6) ? Add sample or test files, meant to be modified with abandon by the user. To make it easier for people to make packages available, I suggest making this information available in a brief ASCII file in the LaTeX distribution, along with the basic information about how to submit something to CTAN. Yes. Putting this in README.uploads in /incoming would be a great help. -- Frank G Bennett, Jr Law Department, SOAS, London Tel: (071)323-6351 email: fbennett@rumple.soas.ac.uk WWW: http://rumple.soas.ac.uk/~fbennett/