[ the gnu list server seems down ATM; expect delays ]
Hi Stefano,
* Stefano Lattarini wrote on Wed, Jul 28, 2010 at 11:07:20AM CEST:
> At Wednesday 28 July 2010, Ralf Wildenhues wrote:
> > But even then, when developing Automake you will need to be extra
> > careful to never let autoconf be invok
At Sunday 08 August 2010, Ralf Wildenhues wrote:
> * Stefano Lattarini wrote on Sun, Aug 08, 2010 at 12:09:52PM CEST:
> > I squashed the following into the first patch:
> >
> > It's OK for you?
>
> Sure.
>
> > > > (BTW, if my understanding is correct, this would make a nice
> > > > addition to H
At Sunday 08 August 2010, Ralf Wildenhues wrote:
> * Stefano Lattarini wrote on Sun, Aug 08, 2010 at 12:53:21PM CEST:
> > At Sunday 08 August 2010, Ralf Wildenhues wrote:
> > > Also, regenerating the tree with Autoconf 2.67 and committing
> > > that separately is preapproved for maint.
> >
> > Cou
At Sunday 08 August 2010, Ralf Wildenhues wrote:
> [ the gnu list server seems down ATM; expect delays ]
>
> Hi Stefano,
>
> * Stefano Lattarini wrote on Wed, Jul 28, 2010 at 11:07:20AM CEST:
> > At Wednesday 28 July 2010, Ralf Wildenhues wrote:
> > > But even then, when developing Automake you w
* Stefano Lattarini wrote on Sun, Aug 08, 2010 at 12:09:52PM CEST:
> I squashed the following into the first patch:
> It's OK for you?
Sure.
> > > (BTW, if my understanding is correct, this would make a nice
> > > addition to HACKING, too).
> >
> > Yep.
> Attached is a follow-up patch that does
* Stefano Lattarini wrote on Sun, Aug 08, 2010 at 12:53:21PM CEST:
> At Sunday 08 August 2010, Ralf Wildenhues wrote:
> > Also, regenerating the tree with Autoconf 2.67 and committing that
> > separately is preapproved for maint.
> Couldn't this cause problems when later merging to master? If yes,
At Wednesday 28 July 2010, Ralf Wildenhues wrote:
> Hello Stefano,
>
> * Stefano Lattarini wrote on Tue, Jul 27, 2010 at 10:58:24PM CEST:
> > Subject: [PATCH 1/2] Bootstrap: let the user choose which
> > autoconf to use.
>
> Well, you should change
>
> > +AUTOCONF=${AUTOCONF-autoconf}
>
> to
>
Hello Stefano,
* Stefano Lattarini wrote on Tue, Jul 27, 2010 at 10:58:24PM CEST:
> Subject: [PATCH 1/2] Bootstrap: let the user choose which autoconf to
> use.
Well, you should change
> +AUTOCONF=${AUTOCONF-autoconf}
to
: ${AUTOCONF=autoconf}
But even then, when developing Automake you wil
On 07/27/2010 03:37 PM, Stefano Lattarini wrote:
>>> I'm used to this variant, with less typing:
>>> : ${AUTOCONF=autoconf}
>>>
>>> But your way works, too.
> Can you confirm it's as portable as the ways suggested in the autoconf
> manual? If yes, do you think it could be an useful addition to th
Hi Eric.
At Tuesday 27 July 2010, Eric Blake wrote:
> On 07/27/2010 03:08 PM, Eric Blake wrote:
> > On 07/27/2010 02:58 PM, Stefano Lattarini wrote:
> >> +# Let user choose which version of autoconf to use.
> >> +AUTOCONF=${AUTOCONF-autoconf}
> >> +
> >
> > I'm used to this variant, with less typ
On 07/27/2010 03:08 PM, Eric Blake wrote:
> On 07/27/2010 02:58 PM, Stefano Lattarini wrote:
>> +# Let user choose which version of autoconf to use.
>> +AUTOCONF=${AUTOCONF-autoconf}
>> +
>
> I'm used to this variant, with less typing:
>
> : ${AUTOCONF=autoconf}
>
> But your way works, too.
Huh
On 07/27/2010 02:58 PM, Stefano Lattarini wrote:
> +# Let user choose which version of autoconf to use.
> +AUTOCONF=${AUTOCONF-autoconf}
> +
I'm used to this variant, with less typing:
: ${AUTOCONF=autoconf}
But your way works, too.
--
Eric Blake ebl...@redhat.com+1-801-349-2682
Libvirt
12 matches
Mail list logo
