packages with binaries
Julian Bradfield writes:
First question: what am I supposed to do with auxiliary programs
(qp-decode, base64-decode etc) that VM likes to have?
Propose to XEmacs Beta that they be added to core. This loses,
though, because 21.4 won't get them.
The problem with distributing in the package is that binary packages
are currently platform-independent; it's not possible to distribute
binaries, and on the platform where it matters most (Windows), the
user will very likely not have the right compiler (or all too often
any compiler at all).
Since XEmacs has built-in base64 functions, I guess the base64
programs are superfluous anyway; and perhaps qp-*code are superfluous
because any qp-encoded message part is likely to be small anyway.
Yes, and yes.
Secondly, is there a way to check out the package infrastructure
without getting the whole of the package sources?
Probably not. But why try to avoid it? You need 50% or so of the
packages to build VM anyway (I think "dired" is new since the version
in our packages):
REQUIRES = xemacs-base mail-lib gnus pgg ecrypto eterm sh-script net-utils ps-print
os-utils bbdb fsf-compat dired
(Gnus is the big pig here.)
Note that using the package builder target in upstream VM is not
acceptable; the Makefile has to use our infrastructure. Otherwise
there is no guarantee that it will even build in Norbert's tree.
BTW, are you really sure you want to do this? Kyle's code was
idiosyncratic (to say the least), but recent VM is a bletcherous mess.
:-(
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta