>>>> "SY" == Steve Youngs
SY> * "Martin" == Martin Buchholz <martin(a)xemacs.org> writes:
>>>> "SY" == Steve
Youngs <youngs(a)xemacs.org> writes:
SY> Does it even need to be in the core distribution at all? I don't mean
SY> that I don't think XEmacs needs ViaVoice support. What I'm saying is,
SY> why can't you package your ViaVoice module separately from the core,
SY> with its own configure/build process?
Martin> That is the "architecturally correct" way to do it. But in practice
Martin> it's probably reasonable to add a hack to our configure.in so that an
Martin> external package doesn't have to maintain one.
SY> I must be missing something here, how does that make any sense?
SY> Wouldn't that restrict the package to being only distributed with
SY> XEmacs, or at least only able to build the package when you build
SY> XEmacs itself?
You build and install XEmacs.
Then you build and install the module, using the installed XEmacs.
Again, the perl example
cd libnet-1.703; perl Makefile.PL; make; make install
is the model. The module gets all of its configuration info from perl.