I agree everything you

Anonymous — Tue, 01 Jan 2008 21:15:44 +0000

I agree everything you wrote.

Thank you.

Updated list of requirements

mfoss — Tue, 01 Jan 2008 20:52:17 +0000

Anonymous wrote:

There is a list in the installation requirements. OpenSSL, Zlib and GBU Iconv are optional.
It might be useful to say what is the purpose of each item and why it is optional.

Yes, the list could be improved. For example:

GNU Make
GCC
libexpat 1.95 or higher
Erlang/OTP R10B-9 up to R11B-5
OpenSSL 0.9.6 or higher, for STARTLS, SASL and SSL encryption. Optional, highly recommended.
Zlib 1.2.3 or higher, for Stream Compression support (XEP-0138). Optional.
GNU Iconv 1.8 or higher, for the IRC Transport (mod_irc). Optional, not needed on systems with GNU libc.

Anonymous wrote:

Are thous installed on linux distributions by default?

The development files probably aren't installed, but they are available for easy installation.
There is some information in this tutorial, maybe it could be included in the guide.

The problem is that if the ejabberd guide documents stuff from other projects (like Debian, Fedora...), then the guide may get obsolete due to changes in those unrelated projects, which we can't control and we may be completely unaware.

Anonymous wrote:

There is no explanation at all about the binary file and how to use it to install, uninstall and upgrade. If this is trivial and there is a link to some tutorial I`ll appreciate that.

If you download and try a binary installer, you will see how to install and uninstall. The upgrade explanation should be added, I'll ask what is the best way to upgrade.

Anonymous wrote:

On the compilation stage it says to:

./configure
make
su
make install

Is this what I should write or should I write make ejabberd for example?
Do I need to be inside the folder where I placed the ejabberd source files when I type ./configure...?

Your question mentions ejabberd, but the question itself is not about ejabberd. Sorry, I have little spare time and I can't spend it on this.

Anonymous wrote:

You might consider add the explanation to the manual (which is very good) because there are things you might consider obvious but to someone who doesn't know linux it's not.

It is unacceptable that the documentation of all the programs in the world explain all of them the same basic things. That would require an unacceptable waste of work to write, that would provide almost zero benefit.

The 'ejabberd Installation and Operation Guide' is about ejabberd, not about Linux, GNU, FreeBSD, Debian or other projects. So, the guide expects some minimum background about general stuff, and concentrate in ejabberd-specific stuff.

ejabberd - Comments for "Installation on linux"

I agree everything you

Updated list of requirements