Re: Rebooting the release process

[Ralf Wildenhues]

* Gary V. Vaughan wrote on Wed, May 05, 2010 at 07:17:38AM CEST:
> On 5 May 2010, at 00:55, Ralf Wildenhues wrote:
> 
> > Somebody noted (off-list) that our bootstrap leaves information specific
> > from the person doing a release in the resulting tarball.  Specifically,
> > you should not have set $GREP, $EGREP, $FGREP, $SED, and some other
> > variables set in the bootstrap script, to some system-specific value,
> > because that will make them end up in the generated libtool script as
> > default value (and also a couple of other scripts).  These may cause
> > errors for others.  This is probably a bug in the bootstrap script or in
> > libltdl/config/general.m4sh, I haven't analyzed.
> 
> Okay thanks.  I'll take a look, though I don't think it's something that
> would make 2.2.8 from HEAD worse than 2.2.6a in the wild, so I think it
> can afford to wait until we've reved.

Well, it's trivial to *avoid* by working around, when you do a release:
  unset GREP FGREP SED ...
  PATH=/some/suitable/tools/bin:$PATH
  export PATH

so please remember to do that, in case the bug isn't fixed beforehand.

Thanks,
Ralf