I am not on the IRC but I agree with Sean here as always. The README and any documentation would need to be updated before removal.
On Wed, May 3, 2023 at 1:48 PM Joshua C. Colp <jc...@sangoma.com> wrote: > Greetings all, > > Sean Bright brought up on IRC the removal of configure from git. This may > be impactful since some users (not necessarily developers) may not > understand the build system when building from branches (not tags or > releases) and become confused when configure is not present which is why I > disagreed with doing so on IRC. I'm curious though what others think of > such a change. I think to be acceptable it would need: > > 1. To regenerate configure if configure.ac has been changed, so that > developers don't have a stale configure > 2. To provide instructions if configure is not present and "make" is run, > I'm on the fence on automatically running it > 3. Releases (and tags) would need to have a generated configure in them > > Thoughts? > > -- > Joshua C. Colp > Asterisk Project Lead > Sangoma Technologies > Check us out at www.sangoma.com and www.asterisk.org > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-dev mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-dev -- - Andrew "lathama" Latham -
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev