On 2019-09-30, sebb wrote: > On Mon, 30 Sep 2019 at 10:25, Stefan Bodewig <bode...@apache.org> wrote:
>> On 2019-09-29, sebb wrote: >>> On Sun, 29 Sep 2019 at 17:21, Matt Sicker <boa...@gmail.com> wrote: >>>> Projects that have a configure script usually include that in the source >>>> distribution but not in the source repository (at least for autotools >>>> users). >>> But is that correct? >> This is what people expect. > But that does not make it right. I'm afraid you and I have different interpretations of "right" :-) > I'll ask again: is the generated config file universally applicable? AFAIR yes, in certain details it may depend on the version of autotools being used but the output is universally applicable in either case. Disclaimer: it's been a long time since I last used autotools. > If so, put it in the source repo. And break with decade old traditions of C-projects, is that "right"? What are the goals of distributing tar balls and of voting on them? IMHO (my opinion, not one that anybody has to share) (1) we want to enable developers to use our products and (2) ensue the ASF is not put at any risk. Personally I don't really see the risk of shipping a configure script that is not part of the SCM repository. Note I haven't voted and don't intend to do so as I am unable to find time to properly vet the release. I've just been offering an opinion and will stop adding to the noise now. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
