Document the autoconf process.

[jlm]

Update the README to describe how to run autoconf to generate the ./configure script.

[stappersg]

It is better as #258 and should be improved:

• Split in "Fear mongering you need Docker" and "Updating the README"
• Add commit messages to the commit summary
• Add sign off by

[stappersg]

And I don't like the white space change.

@jlm if the white space change is important for you, document the why in the commit message. (Preferable in a separate merge request.)

[robbat2]

The whitespace change is fine with me, as we could probably change this to markdown in future.

However it does need a DCO-style signed-off-by line on the PR & commit.

[jlm]

The whitespace is unimportant to me. I think the text explaining how to do it without Docker is worthwhile; I built it on a FreeBSD-based router which had a processor on which Docker was not really practical and someone else might want to do that. The main value of my change is simply that one should run ./autogen-container.sh prior to configure.

Unfortunately I am not familiar with the DCO-style "Signed-off by" line, and don't know how to do that. I am happy for someone else to do that or tell me what to put in more detail.

[robbat2]

The whitespace is unimportant to me. I think the text explaining how to do it without Docker is worthwhile; I built it on a FreeBSD-based router which had a processor on which Docker was not really practical and someone else might want to do that.

The source tarball should already have autoconf & automake completed - did it not work in your environment? [you did not specify if you were building from source].

Unfortunately I am not familiar with the DCO-style "Signed-off by" line, and don't know how to do that. I am happy for someone else to do that or tell me what to put in more detail.

https://www.kernel.org/doc/html/v4.17/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin