Re: [Mailman-Developers] Small contrib script - Autoconf

2018-01-09 Thread Lindsay Haisley
On Wed, 2018-01-10 at 12:13 +0900, Stephen J. Turnbull wrote: > Lindsay Haisley writes: > >  > > The bottom line is this is something that newer autoconf does and >  > > if your autoconf does it, I don't know a way to turn it off. >  >  >  > I looked at the code and that's kinda what I figured. Th

Re: [Mailman-Developers] Small contrib script - Autoconf

2018-01-09 Thread Stephen J. Turnbull
Lindsay Haisley writes: > > The bottom line is this is something that newer autoconf does and > > if your autoconf does it, I don't know a way to turn it off. > > I looked at the code and that's kinda what I figured. Thanks The autotools authors are *extremely* prescriptive, and try to imple

Re: [Mailman-Developers] Small contrib script - Autoconf

2018-01-09 Thread Lindsay Haisley
On Tue, 2018-01-09 at 15:55 -0800, Mark Sapiro wrote: > On 01/07/2018 12:28 PM, Lindsay Haisley wrote: > > > > What's the proper way to run autoconf on configure.in in MM2 in order > > to _not_ generate runstatedir options and code in the configure script? > > I note that the distributed configure

Re: [Mailman-Developers] Small contrib script - Autoconf

2018-01-09 Thread Mark Sapiro
On 01/07/2018 12:28 PM, Lindsay Haisley wrote: > What's the proper way to run autoconf on configure.in in MM2 in order > to _not_ generate runstatedir options and code in the configure script? > I note that the distributed configure script in MM2 doesn't have them, > but simply running autoconf on

Re: [Mailman-Developers] Small contrib script - Autoconf

2018-01-07 Thread Lindsay Haisley
What's the proper way to run autoconf on configure.in in MM2 in order to _not_ generate runstatedir options and code in the configure script? I note that the distributed configure script in MM2 doesn't have them, but simply running autoconf on configure.in produces a configure script that does. Thi

Re: [Mailman-Developers] Small contrib script

2018-01-07 Thread Lindsay Haisley
On Sun, 2018-01-07 at 08:25 -0800, Mark Sapiro wrote: > When you push additional changes to your branch, your merge proposal is > automatically updated. Thanks. > I'll look at the changes in detail within the next few days. Fine. The mailman-config program just provides a bit of convenient infor

Re: [Mailman-Developers] Small contrib script

2018-01-07 Thread Mark Sapiro
On 01/06/2018 09:41 PM, Lindsay Haisley wrote: > > This has been changed as per your suggestion and pushed to Launchpad. I > tried to post a merge request again, after making the changes, but it > was disallowed by the system since I'd already done this for the > original branch push. I presume ma

Re: [Mailman-Developers] Small contrib script

2018-01-06 Thread Lindsay Haisley
On Sat, 2018-01-06 at 17:16 -0800, Mark Sapiro wrote: > The problem with what you currently have done is the configured script > only exists in the source build/contrib directory which will disappear > if one runs 'make distclean' and which is somewhat obscure to find in > any case. > > If this is

Re: [Mailman-Developers] Small contrib script

2018-01-06 Thread Lindsay Haisley
On Sat, 2018-01-06 at 17:16 -0800, Mark Sapiro wrote: > The problem with what you currently have done is the configured script > only exists in the source build/contrib directory which will disappear > if one runs 'make distclean' and which is somewhat obscure to find in > any case. True, that. 

Re: [Mailman-Developers] Small contrib script

2018-01-06 Thread Mark Sapiro
On 01/06/2018 04:28 PM, Lindsay Haisley wrote: > On Sat, 2018-01-06 at 15:25 -0800, Mark Sapiro wrote: >> >> On your branch's code page will be a "Propose for merging" link. Follow >> that, set the Target Branch to ~mailman-coders/mailman/2.1, add a >> description if you like and "Propose Merge" >

Re: [Mailman-Developers] Small contrib script

2018-01-06 Thread Lindsay Haisley
On Sat, 2018-01-06 at 15:25 -0800, Mark Sapiro wrote: > Once you have pushed your branch, go to it in Launchpad. It will be at > or you will also find > it listed at . > > On your branch's code page will be a

Re: [Mailman-Developers] Small contrib script

2018-01-06 Thread Mark Sapiro
On 01/06/2018 02:51 PM, Lindsay Haisley wrote: > > I've made a local copy of the MM 2.1 source tree using 'bzr branch > lp:mailman/2.1" and made appropriate revisions to it incorporating my > mailman-config.py into the contrib directory of the source tree and > modifying configure and configure.in

Re: [Mailman-Developers] Small contrib script

2018-01-06 Thread Lindsay Haisley
On Fri, 2018-01-05 at 20:05 -0800, Mark Sapiro wrote: > On 01/05/2018 12:21 AM, Lindsay Haisley wrote: > > > > > > In what form and fashion should I submit this contribution, which > > consists of about 3 files. I can put these in a tarball and attach > > them, attach them seprately, put them on

Re: [Mailman-Developers] Small contrib script

2018-01-05 Thread Mark Sapiro
On 01/05/2018 12:21 AM, Lindsay Haisley wrote: > > In what form and fashion should I submit this contribution, which > consists of about 3 files. I can put these in a tarball and attach > them, attach them seprately, put them on my public server and post the > URL to this list, or upload them, wha

[Mailman-Developers] Small contrib script

2018-01-05 Thread Lindsay Haisley
I have a small script which may be appropriate for the contrib section in Mailman 2. Basically, it simply assembles a few build-time options, including the option string given to the configure script, and spits them out to stdout when the script is executed. Modifications to configure.in are accom