Strictly speaking, no. XEmacs will build and install just fine without any packages installed. However, only the most basic editing functions will be available with no packages installed, so installing packages is an essential part of making your installed XEmacs _useful_.

No. The name XEmacs is unfortunate in the sense that it is not an X Window System-only version of Emacs. XEmacs has full color support on a color-capable character terminal.

You can't use the same copy of Gnus in both as the Lisp files are byte-compiled to a format which is different depending on which Emacs did the compilation. Get one copy of Gnus for Emacs and one for XEmacs.

To answer the second part of the question: No, you, you don't need Cygwin or MinGW to build or to run XEmacs. But if you have them and want to use them, XEmacs supports these environments. One important reason to support Cygwin is that it lets the MS Windows developers test out their code in a Unix environment without actually having to have a Unix machine around. For this reason alone, Cygwin support is likely to remain supported for a long time in XEmacs.

If you are compiling the source code yourself, what you need for a bare-bones installation is not much: FFmpeg >= 0.4.9-pre1, though you should really just check out the latest FFmpeg library from [FFmpeg CVS]. FFmpeg tends to put out releases very infrequently and so a current development snapshot is likely to be more stable and mature than the last release.

For a concise description of the current situation with XEmacs, see this message from the Cygwin mailing list: 'http://cygwin.com/ml/cygwin/2002-11/msg00609.html'.

You basically just need maven, and it will download other dependencies automatically. The only exception to this are the JavaMail and Java Activation Framework, which are both restricted by a license from Sun.

XEmacs is regularly tested on Linux, Solaris, SunOS, HP/UX, FreeBSD, OpenBSD, BSD/OS aka BSDI, Tru64 aka DEC/OSF, SCO5, and probably others. It should work on all versions of Unix created in the last 10 years or so, perhaps with a bit of work on more obscure platforms to correct bit-rot.

Everything you need to get started is in googleapi.jar. Advanced users may prefer to use their own Java SOAP implementations and use the WSDL file to generate client code.

Yes, you can, but no you do not need to. In fact, we recommend that you use a native-GUI version unless you have a specific need for an X version.

You need Visual C++ 4.2, 5.0, or 6.0 for the native version. (We have some beta testers currently trying to compile with VC.NET, aka version 7.0, but we can't yet report complete success.) For the Cygwin and MinGW versions, you need the Cygwin environment, which comes with GCC, the compiler used for those versions. See section and do I need them to run XEmacs?, for more information on Cygwin and MinGW.

You need a computer that meets the system requirements found here. Also you need to have an internet connection. High speed and low speed both works with Autism Education Online.

Since PDL is just a Perl package you need first of all an installation of Perl on your machine. As of this writing PDL requires version 5.004 of Perl, version 5.004_4 or higher is strongly recommended. More information on where and how to get a Perl installation can be found at the Perl home page http://www.perl.com and at many CPAN sites (if you do not know what CPAN is check the answer to the next question).

Any system capable of running Gnome 2, KDE 3.2, Windows 2000, Mac OS X and later versions should be able to run GIMP. GIMP's biggest appetite is for memory and how much you will need will depend on the how many images you are working with, their resolution, size, the number of layers you use and so on. As a general rule, more is better, but 128MB should be enough to be getting started with.

Any computer that can successfully run JediKnight should be capable of running the core release and all subsequent releases. It has been developed on a Pentium 233 MMX with 32 mb Ram. It was seen running in 3D accelerated mode on an ATI 3D Rage II and Monster 3D II 8 mb video card setup with no problems.

First, you need a computer which is IBM compatible. The computer should have 640 KB of RAM or even more :)) (in some cases it will work with fewer RAM, too, but I would use more). Then, you need a floppy drive, a harddisk or something simular. It would be great to have a keyboard or a mouse and if you want to see something you might need a monitor... but that's all. For those who always were happy with Windows it might be annoying to type a lot at the command prompt.

MiniVend is a complex system requiring the services of other complex pieces of hardware and software. While it can be very easy to install, it is not always. You must look at the ongoing environment as well as just the initial installation. Perl First of all, you need a recent Perl. MiniVend 4 will not run on anything less than Perl 5.005. Perl modules MiniVend will run with a stock Perl, but to use some features of MiniVend (like the MiniMate interface) you will need some extra modules.

A 3DFX-based 3D accelerator card employing the Voodoo, Voodoo Rush, Voodoo2, Banshee or Voodoo3 chipset. (Note: Only D2_3DFX v1.06b supports Voodoo2 and above.)

In all other cases, such as running DenyHosts from cron then technically speaking, no. However, in order to run DenyHosts as non-root you must ensure that you have read-permissions on the /var/log/ sshd server logs. Alternatively, you can copy them to a directory where you do have read-permissions. Also, in order for DenyHosts to block hosts, it needs write permissions for the /etc/hosts.deny file. DenyHosts will gladly run without being able to update this file.

EzASPSite? requires web space on a web server that supports ASP 2.0 or above. Without Microsoft ASP 2.0 or above support you can NOT use this application.

To run Xen and a single OS from a binary release you need install no extra packages. To build Xen, XenLinux and documentation from source you will need: make, libncurses5-dev, libncurses5, gcc, libc6-dev, zlib1g-dev, python, python-dev, python-twisted, openssl, openssl-dev, bridge-utils, iproute, libcurl3, libcurl3-dev, bzip2, module-init-tools, latex, latex2html, transfig, and tgif.

If you want to compile QEMU from source, then you must. This is required. If you are using a binary package however, then it's not necessary (but it doesn't hurt either).

Most software from the Free Software Foundation compiles and runs on 3B2s with little or no modification. The following are exceptions and their reasons. Please prove me wrong, I'd love to have some of this stuff on my 3B2 as well. gdb - GNU Debugger No configuration files for WE32K processor. libg++ - C++ Libraries The g++ compiler produces invalid assembler code for one of the modules.

You do not need to worry about installing any special packages. If a package is required and your server does not have it, then the install script will download it from the Internet. If you really want to know what packages it uses, please have a peek at the install script. It uses the yum utility to install packages.

Many setup routines historically were a black box where the administrator or installation engineer would not know what was happening at the time of installation. With .MSI technology the system administrator has total control of all installation and Uninstall routines due to transactional install. Centralised Deployment of packaged applications will reduce the total cost of ownership (TCO), Reducing support costs