Re: [PATCH] x-symbol should have a _real_ binary package
Christoph Wedler <wedler(a)fmi.uni-passau.de> writes:
Hm, if you want to remove everything, why not use
rm {etc,lisp,...}/PACKAGE/* ?
That is what we used to do but no longer. All the files belonging to
the package should be in the MANIFEST file. That's why it there. This
is mainly to make sure the automated package maintenance tools can do
the right thing. Hopefully the MANIFEST files will even contain
md5sums in the future.
Now if you really want to be a bad boy you can put the generated files
in the MANIFEST file but NOT include them in the distribution.
JR> The pcf font files should come bundled with the binary
release.
Hm, I've though of that. But this would add 200k (tarred) to the binary
package (versus 1x "make" taking 5s)...
I think this is a minor concern. I binary package should be exactly
that, just some stuff to put somewhere. Maybe in the future XEmacs
will allow scripts to be run before and after installing/removing like
real packagers. If you want to trade off download for compile time,
get the source.
much about this font stuff. Thus, if more people think that putting
the
pcf font files with the binary package, this would be fine with me.
I think with the current state of the package system this is the best
solution.
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.
I have though of that, too. (Jan, was it you who said it is better not
to split the distribution?)
I am not sure. It does create some hassle (mainly because the package
system does not support dependencies now). However the hassle is not
that BIG. Maybe you can make the x-symbol package signal a warning if
there is no fonts package installed.
But I think down-loading a second package
is more work than to type "make" once. How would this work with
pui?
When xsymbol is part of the package-index database downloading a
second package is a matter of typing 'RET' and 'g'.
Jan