Re: Taking over production of emacs20 package.
Hi,
Also consider the fact that all maintainers may not have
enough resources to have all possible flavours of Emacsen on their
machines (Xemacs19, Xemacs20, emacs19, emacs20, emacs20-no-mule,
Xemacs-no-mule, ...), and keep track of which versions were elc
compatible anyway.
On the other hand, some packages (Quassia gnus and VM are examples)
that do funny things in the Makefile in order to compile the el
files; it is not just a matter of
# $(EMACS) -batch -f batch-byte-compile *.el
Alternately, each maintainer can maintain a package for one
flavour of Emacs ;-(, and have co-maintainers for ther
flavours. Autocompilation may not be quite as trivial as it may
seem (though by no means impossible).
manoj
ps. Oh, I, too, thought of making public my private quassia gnus
package, but it is way too volatile, I think, for general
distribution. It is not 10M, BTW, just 5675K.
--
"I honestly believe that the doctrine of hell was born in the
glittering eyes of snakes that run in frightful coils watching for
their prey. I believe it was born with the yelping, howling,
growling and snarling of wild beasts... I despise it, I defy it, and
I hate it." Robert G. Ingersoll
Manoj Srivastava <srivasta@acm.org> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: