Windows configure "issues"
neugens.limasoftware at gmail.com
Tue May 21 23:02:10 UTC 2013
I fully agree with this point of view.
I don't think that this conflict with the idea of a wiki companion, this
can be done and surely would be of help, but copy-paste instructions should
be with the code. I also think that since we need to keep in sync the
readme with the wiki, the problem with the overhead of the process doesn't
really change (with the risk of then having an outdated readme).
Il giorno 22/mag/2013 00:26, <mark.reinhold at oracle.com> ha scritto:
> 2013/5/21 6:54 -0700, gnu.andrew at redhat.com:
> >> On 05/21/2013 04:55 PM, Volker Simonis wrote:
> >>> I always felt that having the build instructions checked in into the
> >>> repository is somewhat to heavyweight.
> >> There are two good reasons to do this.
> >> Firstly, it's a free software tradition: I expect to find a README with
> >> build instructions in the repo. Secondly, the build instructions will
> >> change over time, so of they're on a Wiki there will have to be
> >> multiple versions.
> >> Andrew.
> > Another reason is it makes the software self-contained; I don't need
> > access and a web browser to be able to build it.
> I agree, on all three counts. How-to-build documents, just like unit
> tests, belong with the code to which they apply. Posting them on a
> wiki just increases inconvenience and invites confusion.
> - Mark
More information about the build-dev