You have a point but you cant possibly make a documentation which
describes every possible situation. You can give the basics and let the
user use it as required.

I think the most important thing which needs documentation is the
./configure switches of these programs. 

The rest is quite trivial, there is more than enough examples in google

So I find it difficult to have a complete installation manual. But yet we
can compile in the working manuals in some web page or something. Like the
one I sent. It works for me and for the functionalites I need. If somebody
needs the exactly same stuff, why not share :) I dont mind


On Wed, 13 Aug 2003, Ron Guerin wrote:

> Greetings all,
> I know some of you (like myself) have probably poked around in the
> vpopmail docs and maybe fixed a spelling error or added a new command
> line option to your local documentation.
> Others may have prepared HOWTO documents describing their setup, as I
> also was thinking of doing.
> Wouldn't it be nice if we could get together and produce comprehensive
> vpopmail documentation?  Wouldn't it be even nicer if we could
> distribute that documentation with vpopmail?
> We can!  And I'd like to start the ball rolling by asking everyone on
> the list if they've got some documentation they've written stashed on
> their system that they'd like to contribute to the project.
> Once we know what we have to start with, we can figure out what to do
> next.
> - Ron

Reply via email to