Re: --with-included-foo={yes,no} and which foo.h to use?

[Julian Foad]

Stepan Kasal wrote:
> On Thu, Jul 07, 2005 at 02:33:59AM -0400, Charles Levert wrote:
> > Updating to glibc's regex.c will allow us to
> > progress in fixing RE_ICASE bugs now, and maybe
> > others as well.  That why I can't see one being
> > a priority without the other.
>
> Well, it's obvious that with the old regex.c we cannot fully fix all
> the icase problems.  We can just fix the most obvious.
>
> Full icase fix is tied to new regex.
>
> But there is no need to fix _all_ problems in the _next_ release.

Correct.

> I wanted to create an improved version of 2.5.1, which would be ready
> for people which for some reason cannot use the new regex.c.
> (Perhaps the new regex won't compile on an ancient platform, or they
> will have to use a regex which shows the inefficiency of the new
> regex, perhaps something like the original palindrome regex, which
> takes ages to run with new regex.)
>
> In short, I wanted to squeeze maximum from the old regex before we
> move to new regex.  I think that the new regex might open a can of worms.

If certain regexes like the palindrome will definitely behave worse, and there 
is a significant possibility of other as-yet-unknown problems for some people, 
I agree we should release 2.5.2 first.  There are already enough fixes to make 
it worthwhile.

But do you have the time to make that release very soon?  If not (or even if 
you do), could we just make a 2.5.2 branch from the current CVS code now, and 
then tidy it up (such as disabling some tests) and release it at our leisure 
while the trunk gets continuing development (such as the new regex.c) towards 2.6?

- Julian


[...]
> So my opinion still is that it would be better to release what we have
> now as 2.5.2, no matter how many bugs are remaining.
>
> But, of course, your vote should have more weight than mine, as you did
> more work.
>
> Stepan