Re: libjava build failure with read-only source tree
"Jan Beulich" <[email protected]>
| Newsgroups | gmane.comp.gcc.java.devel |
|---|---|
| Message-ID | <[email protected]> |
>>> On 29.09.11 at 10:39, Bryce McKinlay <[email protected]> wrote: > On Thu, Sep 29, 2011 at 9:18 AM, Jan Beulich <[email protected]> wrote: > >> As this isn't the first time I encounter this in the libjava subtree, can it >> be made a requirement for testing changes that they must work with >> fully read-only source trees? And/or if there's some sort of automatic >> testing in place, could that be adjusted to include a respective check? > > It would be heavy-handed to require every contributor to test patches > with a read-only tree. We don't want to make the patch submission > process any more onerous than it already is. I certainly realize that. But this wouldn't be needed for all submissions, just such that alter the tree layout of the build tree. Btw., the patch that I had embedded in the original mail works, but as there's no maintainer listed for libjava in ./MAINTAINERS I'm entirely unclear who I would need to turn to in order to get approval to commit this. Jan