One risk of having the configure script checked into the repository is that people will misunderstand that it's generated, and spend a lot of time manually solving some problem, only to have their PR rejected because the changes are in the wrong place.
We've seen this sort of thing from time to time on cyrus-imapd; these days we generally try not to commit things that are generated. We do make sure to include the pregenerated files in release tarballs, where it makes sense to do so, so that people installing the software don't need to also have the tools to generate them. But we assume that if people are building from git, rather than a release, then it won't be any additional burden on them to need to "autoreconf -is" as well, for example. Consider this a "general thought" rather than an "objection". I'm not familiar with the cyrus-sasl project's particular needs, but I imagine they probably differ from cyrus-imapd's. Cheers, ellie ------------------------------------------ Cyrus: Devel Permalink: https://cyrus.topicbox.com/groups/devel/Te20b7276729affa7-Ma18d28f9f549596032a21952 Delivery options: https://cyrus.topicbox.com/groups/devel/subscription
