Windows configure "issues"
gnu.andrew at redhat.com
Tue May 21 21:11:19 UTC 2013
----- Original Message -----
> On Tue, May 21, 2013 at 9:00 PM, Andrew Haley <aph at 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,..).
True. But it's the process that needs to be changed in that case, because
it also applies to other patches. Working around it doesn't help.
A sponsor is only needed for those without commit access. It's pretty easy
to get a review. Are we any further to being able to get access to the bug
system, which is long overdue?
Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)
PGP Key: 248BDC07 (https://keys.indymedia.org/)
Fingerprint = EC5A 1F5E C0AD 1D15 8F1F 8F91 3B96 A578 248B DC07
More information about the build-dev