>>>> "ST" == Stephen J Turnbull
>>>> "MK" == Mike Kupfer writes:
MK> On the other hand, I don't see a big problem telling package
MK> maintainers and anyone else who builds from CVS that they'll need to
MK> upgrade their installation of 21.4.
ST> Even if they've got a corporate IT dept breathing down their neck?
ST> I know several people who work in environments where it's much
ST> easier to get approval to add or upgrade a single Lisp package than
ST> to get all of XEmacs upgraded. Whether they use our package format
ST> for distribution of those I don't know.
I guess that's the key question. If they're actually rebuilding from
CVS, then I'll reconsider my position. If they're just downloading
prebuilt packages, they wouldn't be affected by the requirement to
ST> It affects anybody who wants to build auto-autoloads for ede and
ST> semantic (and maybe other packages by now), whether in the package
ST> system or not. You agree that's something that a "typical user"
ST> of ede and semantic would want to do?
I'm afraid I don't know enough about typical XEmacs users. I think I
knew what an auto-autoloads file was before signing up to be a package
maintainer, but I certainly never built one.
ST>  The problem is that these packages add a bunch of
ST> "defsomethings" that need to be treated as defuns in auto-autoload
ST> files, which 21.4 doesn't know about.
Okay. Thanks for adding these clarifying remarks, by the way. I
remember trying to follow the discussions when this issue first came up
and getting totally lost.
XEmacs-Beta mailing list