From xemacs-m  Sun Aug 10 04:32:50 1997
Received: from altair.xemacs.org (steve@xemacs.miranova.com [206.190.83.19])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id EAA15124
	for <xemacs-beta@xemacs.org>; Sun, 10 Aug 1997 04:32:47 -0500 (CDT)
Received: (from steve@localhost)
	by altair.xemacs.org (8.8.6/8.8.6) id CAA16679;
	Sun, 10 Aug 1997 02:37:12 -0700
Mail-Copies-To: never
To: xemacs-beta@xemacs.org
Subject: Re: strokes.el --- `package-path'
References: <199708100056.UAA23360@w20-575-57.MIT.EDU> <877mduv37h.fsf@bittersweet.inetarena.com>
X-Face: `'%\i;ySOu]g?NlziJSk_$&@]KP`}~PEQPjZ5;nxSaDW_o$4+4%Ab]%Ifw3ZR;7TIT3,O,'
 @2{L;]ox6kc;$_5kU'n**9vFg-]eV~GbxSVCx|(s%uR[],*:^WKmC`B}(;|k9/m]gwt?&`t;^rfCJg
 khHH>pP1W\)xM0U@!FNDD72{3fDP$PkBhx^7Z?-WxH6DbFN:QOnT`llzW}VGdYv;n9lzljQvKTIBhQ
 YuV
X-Attribution: sb
From: SL Baur <steve@xemacs.org>
In-Reply-To: karlheg+xemacs@inetarena.com's message of "10 Aug 1997 01:42:42 -0700"
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: multipart/mixed;
 boundary="Multipart_Sun_Aug_10_02:37:12_1997-1"
Content-Transfer-Encoding: 7bit
Date: 10 Aug 1997 02:37:12 -0700
Message-ID: <m2u3gy8jlj.fsf@altair.xemacs.org>
Lines: 86
X-Mailer: Gnus v5.4.64/XEmacs 20.3(beta18) - "Bratislava"

--Multipart_Sun_Aug_10_02:37:12_1997-1
Content-Type: text/plain; charset=US-ASCII

Karl M Hegbloom <karlheg+xemacs@inetarena.com> writes:

> You should have
> a Makefile in lisp/strokes, with an `autoloads' rule, that looks
> something like:

> autoloads:
> 	$XEMACS -batch -q -l autoload -f batch-update-directory .

> compile: autoloads
> 	$XEMACS -batch -f batch-byte-recompile-directory .

> ... so that the auto-autoloads file is rebuilt using your
> ;;;###autoload cookies, and gets byte-compiled[1].  Then, when XEmacs
> is redumped, strokes will be there, ready to autoload.

>  This puts control of a package in the author or maintainer's hands,
> where it belongs; I think that is one intention of the packages
> directory.


--Multipart_Sun_Aug_10_02:37:12_1997-1
Content-Type: audio/basic
Content-Disposition: attachment; filename="kiss.au"
Content-Transfer-Encoding: base64

LnNuZAAAABwAAAK3AAAAAQAAH0wAAAABR1chAGf/Z2f//+fnU9vJSdtnProisizJ2zatNrBN
01v/W1NnOLwuxVPJ2z6vPLzTLZxJJZ5bJZ8yMJ4uKJ8qOqkqTbYrycUr06YmNqS8Ir7BLtPJ
J64ySbYrvNs2zck6U6wwzaYjoDxToyGumxqoqiOmwS7NsCG42x2juA+eSRmPDy6VGkGbLUWq
NjyfKsGoHqmtH7KvG6xFLLy2WzqyNs3BOK46SbYwsjpFrB+uSSywJ7RnJ6s8QbQmwZQNnTgi
oRmqQSSqH7RFMLQvwU1FwedbU7owvCrFuB+vLOfBNsVT2y+QHsm6LM0voxzN0yuuKLC8LtO8
ME3BRdtTRc1Bvi6sLJcpzcEyrCCsI7I4rTao5ziuLrw8W7wouKEftBibwQ6ZEaZNpiytKmfT
uDCoOLwlryCsLKg2qTzJNmdnQf+rKr4ksjjb21vJSbo8MKpJwbJbvDBbLrxTuudFQUGqOj64
NKY62y7FIpMfkiKwILY8uNsw5//NU1PNTT7BTefnvDQ856skmSecIqoZqhqTHZEemxSuILRn
nSKtJrw4xS2lxdvbZy64PrJBOpwsqSfJNr48oCyvHp3bKEXbSb7JZza+OM1NPJ4ekiWhF6oX
nTSwPK4fpxyqW7AvvivTvD7npTLTMronnyuvOiqRGpImrResH5/TlhGuHKMioEmgHskwxbrF
0zQv/8GaDJYtpRuuNrr/QbQmxT60000+Ptu6W65nHqQwtD5Nobogsi+eLbYaqP/nOrAuTS6a
IckwpS+vHrioRUktrzQptpxJPh+iNJoi/6C+sC8+uCNJOmcm01PBzUXb28FBQc2um2edF58N
pSiqMiWrJ6e+rdssOFMwNDo4ybakG0n/Os1TPk0+/0VJSVNb/1v//1tbZ6y4TSskNMGyzUlJ
/1v/2/+uslMqKjjTvrrFTUlJU9vF

--Multipart_Sun_Aug_10_02:37:12_1997-1
Content-Type: text/plain; charset=US-ASCII


>  It's working well with AucTex, once I patched the autoload cookies
> back into it, and removed the ones in the old TeX mode.  I've also got
> `elib' set up[2], and someone has done bbdb.  Obviously Gnus is
> working too.  :-)


> Footnotes: 
> [1]  Will yous tell me if that's not quite right?  It's not tested.

Yes, you're correct.  The procedures nned to be tested before they get
inflicted on unsuspecting package developers.  I had been hoping to
prototype it with Quassia Gnus but that doesn't appear to be an option 
now, so I'll have to choose some other package to start with.  The
only package being updated (fairly) frequently now is custom and that
won't be package-ized until at least 20.4 (if ever).

The requirements I have for prototyping this are:

1. A developmental version of a widely used Emacs/XEmacs lisp package
2. Frequent releases
3. The candidate package should include both lisp and texinfo
   documentation, and preferably something in data-dir

(skk and mew would be two candidates if their respective developers
were amenable -- I'm prepared to work with one or both).

> [2]  Should I upload this to my web site?  It's not really mine, but is
>      GPL, AFAICT so perhaps I shall...  Yes.  I will.  It will be in
>      http://www.inetarena.com/~karlheg/Public/site-lisp shortly.

Put Colin's bbdb package there too until its disposition is decided
on.

I would like all package distributions to be digitally signed,
preferably with PGP.  I'm open to suggestions on how to build up an
XEmacs web of trust.

--Multipart_Sun_Aug_10_02:37:12_1997-1--

