Updating Readline

Updating Readline

[Eli Zaretskii]

This attempt to update Readline in GDB:

  https://sourceware.org/ml/gdb-patches/2015-07/msg00422.html

ended up not doing it.  We are still at Readline 6.2, AFAICT.

Is there any hope of updating to a newer Readline?  Please?

Re: Updating Readline

[Patrick Palka]

On Tue, Feb 16, 2016 at 11:41 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> This attempt to update Readline in GDB:
>
>   https://sourceware.org/ml/gdb-patches/2015-07/msg00422.html
>
> ended up not doing it.  We are still at Readline 6.2, AFAICT.
>
> Is there any hope of updating to a newer Readline?  Please?

Updating to readline 7.0 (alpha) causes a lot of testsuite regressions
on a number of (non-x86) platforms.  It may be safer to first upgrade
to readline 6.3 but in that case there are some local patches that
have to be preserved.  So it raises the question of how the ChangeLog
should reflect that some local patches are preserved across the
upgrade, while other local patches are dropped since they've been
applied upstream.  The idea is to make it easy to tell which local
patches are currently applied against our upstream copy of readline
especially across upgrades.

Re: Updating Readline

[Eli Zaretskii]

> From: Patrick Palka <patrick@parcs.ath.cx>
> Date: Tue, 16 Feb 2016 12:23:24 -0500
> Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
> 
> On Tue, Feb 16, 2016 at 11:41 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > This attempt to update Readline in GDB:
> >
> >   https://sourceware.org/ml/gdb-patches/2015-07/msg00422.html
> >
> > ended up not doing it.  We are still at Readline 6.2, AFAICT.
> >
> > Is there any hope of updating to a newer Readline?  Please?
> 
> Updating to readline 7.0 (alpha) causes a lot of testsuite regressions
> on a number of (non-x86) platforms.

Yes, I know.  That old thread says that, and it was the reason the
upgrade never happened back then.

> It may be safer to first upgrade to readline 6.3

Does it make sense to upgrade to 6.3 when 7.0 is already in beta?  We
do want eventually start using a newer Readline, I hope.  If so, we
need to start fixing the problems the update causes, otherwise we will
be left behind.  Either our tests need to be amended or Readline 7.0 is
not a simple drop-in replacement, and more of our code needs to be
changed.

But I don't think it makes sense to do nothing, or start using an old
version of Readline.  We will be just deferring the problem for later,
and it won't fix itself, I think.

Thanks.