Hi Gary.
On Sunday 23 October 2011, Gary V wrote:
> Hi Stefano,
>
> In practice, I prefer to:
>
> git status
>
> git clean -f -x -d
> ./bootstrap --gnulib-srcdir=../gnulib && ./configure --disable-nls
>
> This is way faster, but relies on my discretion. Like Jim, I'm leary of
> recommen
Hi Stefano,
On 23 Oct 2011, at 00:20, Stefano Lattarini wrote:
> Hi everybody. Just my two cents about this matter ...
>
> On Saturday 22 October 2011, Bruno Haible wrote:
>> Gary V. Vaughan wrote:
> Running the (potentially) outdated configure, to build a (potentially)
> outdated Makefi
On Saturday 22 October 2011, Jim Meyering wrote:
> Stefano Lattarini wrote:
> >> make -k maintainer-clean # Clean up previous build artefacts
> >> ./configure
> >> make maintainer-clean# Clean up previous build artefacts
> >> git checkout master
> >> git pull origin master # don't t
Stefano Lattarini wrote:
> Hi everybody. Just my two cents about this matter ...
>
> On Saturday 22 October 2011, Bruno Haible wrote:
>> Gary V. Vaughan wrote:
>> > >> Running the (potentially) outdated configure, to build a (potentially)
>> > >> outdated Makefile, which may very well rerun acloc
Hi everybody. Just my two cents about this matter ...
On Saturday 22 October 2011, Bruno Haible wrote:
> Gary V. Vaughan wrote:
> > >> Running the (potentially) outdated configure, to build a (potentially)
> > >> outdated Makefile, which may very well rerun aclocal, automake, autoconf
> > >> etc
Gary V. Vaughan wrote:
...
> Okay to push?
Yes, but with the following changes applied:
use this instead, per today's discussion:
make -k maintainer-clean || { ./configure && make maintainer-clean; }
and change "incase" to "in case" in the commit log and ChangeLog:
> readme-release: several
Hi Jim,
> > ./configure
> > make maintainer-clean# Clean up previous build artefacts
>
> What's the point of rerunning configure and maintainer-clean?
I sometimes do "make distclean" in a subdirectory. This removes some
but not all Makefiles. "make -k maintainer-clean" will thus fail and
Bruno Haible wrote:
> Gary V. Vaughan wrote:
>> >> Running the (potentially) outdated configure, to build a (potentially)
>> >> outdated Makefile, which may very well rerun aclocal, automake, autoconf
>> >> etc just to call the maintainer-clean rule, and then blow it all away
>> >> in the next step
Hi Jim,
On 22 Oct 2011, at 17:15, Jim Meyering wrote:
> Gary V. Vaughan wrote:
>>
>> If you want to clean the cruft out of your working directories before
>> starting the release process, you should do it before you change branches
>> and merge changes from upstream, using the Makefile that you a
Hi Jim,
Gary V. Vaughan wrote:
> >> Running the (potentially) outdated configure, to build a (potentially)
> >> outdated Makefile, which may very well rerun aclocal, automake, autoconf
> >> etc just to call the maintainer-clean rule, and then blow it all away
> >> in the next step with a bootstrap
Gary V. Vaughan wrote:
> Hi Jim,
>
> On 22 Oct 2011, at 03:06, Jim Meyering wrote:
>> Gary V. Vaughan wrote:
>>> As it stands (without this patch), README-release recommends:
>>>
>>> git checkout master
>>> git pull
>>> ./configure
>>> make maintainer-clean
>>> ./bootstrap
>>>
>>> Running the
Hi Jim,
On 22 Oct 2011, at 03:06, Jim Meyering wrote:
> Gary V. Vaughan wrote:
>> As it stands (without this patch), README-release recommends:
>>
>> git checkout master
>> git pull
>> ./configure
>> make maintainer-clean
>> ./bootstrap
>>
>> Running the (potentially) outdated configure, to
Gary V. Vaughan wrote:
...
>>> -* Run ./configure && make maintainer-clean
>>
>> Why do you want to remove the "make maintainer-clean"?
>> I saw no justification, so maybe it's an accident.
>
> Hmm... half and half. Here's the relevant bit of ChangeLog:
>
> + Don't try to run ./configure right
Hi Jim,
On 21 Oct 2011, at 15:17, Jim Meyering wrote:
> Gary V. Vaughan wrote:
>> I made these changes in gnulib-local/top/README-release while making
>> a start at leveraging the gnulib release machinery into GNU Libtool,
>> but they seem generally applicable too.
>
> Thanks for the suggestions.
On 21 Oct 2011, at 16:11, Bruno Haible wrote:
> Hi Gary,
Hi Bruno,
Thanks for the feedback.
>> Set a neutral locale for rolling the release tarballs.
>
> I disagree with this advice. Yes, the first time you run a "make distcheck"
> in a German locale, 'makeinfo' may put German strings into your
Hi Gary,
> Set a neutral locale for rolling the release tarballs.
I disagree with this advice. Yes, the first time you run a "make distcheck"
in a German locale, 'makeinfo' may put German strings into your formatted
documentation. But "make distcheck" ought to work for any user as well
as for you
Gary V. Vaughan wrote:
> I made these changes in gnulib-local/top/README-release while making
> a start at leveraging the gnulib release machinery into GNU Libtool,
> but they seem generally applicable too.
Thanks for the suggestions.
However, it's not quite ready.
> Okay to push?
I'm glad you a
I made these changes in gnulib-local/top/README-release while making
a start at leveraging the gnulib release machinery into GNU Libtool,
but they seem generally applicable too.
Okay to push?
(NOTE: I doubt this will work with `git apply-patch` since I pasted
it together from bits of manual diffs
18 matches
Mail list logo
