bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] README-release improvements


From: Stefano Lattarini
Subject: Re: [PATCH] README-release improvements
Date: Sat, 22 Oct 2011 20:07:37 +0200
User-agent: KMail/1.13.7 (Linux/2.6.30-2-686; KDE/4.6.5; i686; ; )

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 try (perhaps fail) to pull other 
> >> branches
> >>   ./bootstrap              # rerun autotools explicitly on latest sources
> >>   ./configure              # regenerate Makefile explicitly -"-   -"-
> >>
> > At this point, wouldn't it be simpler (and maybe safer) to clone the git
> > repository in a new directory, and simply do "./bootstrap && ./configure"
> > from there?
> 
> Hi Stefano,
> 
> That would be simpler, but might end up masking a problem in the long run.
> I want to be sure that my usual build directory has the latest versions
> of byproducts produced by tools like bison.
> 
> With an explicit "make maintainerclean" at least just before each release,
> I can't accidentally continue to use an old generated file for too long.
> 
OK.  But I still think that making sure to produce a correct distribution
tarball should take precedence over ensuring the generated files in your
tree are up-to-date ...  Anyway, we are only talking about suggestions in
the README here, not mandated or scripted rules, so no big deal for me.

Regards,
  Stefano



reply via email to

[Prev in Thread] Current Thread [Next in Thread]