Re: User submitted Install How To
Raymond Toy writes:
steven> 6. Choosing command line options for ./configure.
steven> There are many command line options you can
steven> set. Almost everyone will have at least some
steven> options to specify and almost nobody will be able
steven> to install XEmacs without specifying some options.
Isn't this supposed to work without options?
It will work, but probably will result in a suboptimal installation.
Granted the default installation directory is probably wrong,
AFAIK /usr/local is still the recommended place for local builds in
FHS. Perhaps that's not so on Solaris, but with MacPorts occupying
/opt/local by default, it seems like the obvious place on Mac. I
suspect --prefix will nevertheless often be desirable, but an
installation in /usr/local should not actually cause problems.
but xemacs should build and work. Nowadays, all I specify is
--prefix, --with-mule, and --with-xft, and the latter two are only
because I want mule and xft support.
But that's precisely Steven's point, I suppose. There are still
issues with Xft that prevent me from making it default, but it really
should be default. I'm tempted to make Mule default, but it does have
performance issues. Still, I would expect that the vast majority of
Linux and Mac users will want Xft, and a substantial minority needs
Mule.
steven> 9. To bootstrap the packaging system, download 2
files:
I also never go hunting around for the packages and just grab the
xemacs and mule sumo tarballs. If you're new to xemacs, this is much
easier.
Yeah, -1 on bootstrapping packages. New users really should use the
SUMOs. They're not even large by modern standards.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta