JV> Christoph Wedler <wedler(a)fmi.uni-passau.de&gt; writes: JV> That is what we used to do but no longer. All the files belonging JV> to the package should be in the MANIFEST file. That's why it JV> there. [...] Now if you really want to be a bad boy you can put JV> the generated files in the MANIFEST file but NOT include them in JV> the distribution. What about the created lex files and executables for conversion in etc/x-symbol/bin/SYSCONFIG/ They get created after "M-x x-symbol-exec-create" under XEmacs/no-Mule. I cannot make them appear in the MANIFEST because SYSCONFIG is the value of `system-configuration' and users might have defined their own token languages (BTW, language "Isabelle Symbol" is in preparation, to be distributed with the Emacs package ProofGeneral). Note that this is not a problem of X-Symbol alone: M-x TeX-auto-generate-global creates files in etc/auctex/auto/ which don't appear in the MANIFEST. IMHO, the best thing would be that packages can have their own private directory in the package hierarchy which they could use at will, e.g. data/{auctex,x-symbol}. BTW, it would be only 67k if faces would have a face property `baseline-shift'... JV> I think with the current state of the package system this is the JV> best solution. OK, I will include them. Although the real benefit (no user interaction during installation) is only there with sth like Jim's code for an Elisp function set-font-path... JR> It might be better to have a separate font package JR> x-symbol-fonts-pkg.tar.gz to help save down-loading time during an JR> upgrade. JV> I am not sure. It does create some hassle (mainly because the package JV> system does not support dependencies now). However the hassle is not JV> that BIG. OK, if there is a general way how to handle additional fonts with the package system, I will probably split the distribution (but not now). JV> Maybe you can make the x-symbol package signal a warning if there JV> is no fonts package installed. It does already. - Christoph