On Tue, May 21, 2013 at 9:00 PM, Andrew Haley <a...@redhat.com> wrote:
> 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. > > You're right, but the problem is that the process of updating the instructions is much too heavyweight (getting a BugID, getting reviews, getting a sponsor who will push the changes,..). The other problem is that there exist so many different OS releases/distributions and compiler versions which people may use for building that I'm afraid the "official" README in the repo will never cover them all. So I'd rather take a pragmatic approach of having more build documentation in a central place in the Wiki than having a super-accurate documentation in the repository for a system nobody can even set up today (e.g. because the software mentioned there isn't available anymore). I therefore like Kelly's suggestion of having a "bare bones" version in the repository and more details and updates in the Wiki. > Andrew. > > > >
