From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/8] Upgrade readline
Date: Mon, 12 Aug 2019 19:46:00 -0000 [thread overview]
Message-ID: <87k1bi418b.fsf@redhat.com> (raw)
In-Reply-To: <87mugk7oy0.fsf@tromey.com> (Tom Tromey's message of "Wed, 07 Aug 2019 13:31:03 -0600")
On Wednesday, August 07 2019, Tom Tromey wrote:
>>>>>> "Sergio" == Sergio Durigan Junior <sergiodj@redhat.com> writes:
>
> Sergio> I'm in favour of bumping the readline version to 7 (note that Debian
> Sergio> oldstable, i.e., wheezy, which was released 4+ years ago, already ships
> Sergio> with readline 7), and (eventually) just get rid of our local copy.
>
> We talked about that briefly on irc yesterday too.
Yes (for a different value of "yesterday" now).
> I wonder if we really could get rid of the local copy. I mean,
> obviously we could, but would it be a problem for anybody?
[ /me puts his downstream hat ]
I guess it depends. If the person is building GDB on a system that
doesn't offer readline-dev or a similar package, then it can be a
"problem" in the sense that he or she will have to compile readline by
hand, probably.
Otherwise, I don't see how it can be a problem. As I pointed out during
the IRC discussion, the two major GNU distros (Fedora and Debian) are
already compiling their GDB packages using --with-system-readline, so,
in a way, our readline copy is not needed. These distros also provide
readline-dev, which makes it very easy for users to compile their own
GDBs without using our local readline copy.
OOC, I went to check how Arch[GNU/]Linux compiles GDB, and they are also
using --with-system-readline.
> We could treat it a few ways. One would be like libiconv: keep the
> top-level configury around so it's possible to drop the readline sources
> into the tree and then build.
That'd be a good compromise, IMO.
> Another way would be to use something like guix for these dependencies.
> I don't know if that works on all the hosts that we care about.
>
> The guix way is attractive since it seems vaguely analogous to using
> "cargo" in the Rust world. In particular if we could do something like
> this, maybe we could be less conservative about bringing in new
> dependencies.
The guix idea seems awesome, but that's because I like guix ;-). If I'm
honest, I don't like the idea of keeping readline in-tree at all; I'd
prefer to have guix manage some "obscure" dependency that can be missing
in some system. But that's me and my "let's not turn everything into a
flatpak" feeling ;-).
> I think either of these solutions would also fix the bug we found with
> moving gdbsupport to the top level (i.e. that it interacts poorly with
> --with-system-readline). (I never got a response to that note, so if
> you're reading this, I'd appreciate a quick look at that as well.)
I'll take a look, thanks for mentioning!
Cheers,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2019-08-12 19:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 20:43 Tom Tromey
2019-08-06 20:43 ` [PATCH 4/8] Remove gdb workaround from readline/xfree.c Tom Tromey
2019-08-06 20:43 ` [PATCH 8/8] Require readline 7 or newer Tom Tromey
2019-08-07 2:27 ` Eli Zaretskii
2019-08-07 14:42 ` Pedro Alves
2019-08-07 22:31 ` Tom Tromey
2019-08-08 2:37 ` Eli Zaretskii
2019-08-08 11:26 ` Pedro Alves
2019-08-08 11:29 ` Pedro Alves
2019-08-08 20:38 ` Tom Tromey
2019-08-07 14:45 ` Pedro Alves
2019-08-06 20:43 ` [PATCH 2/8] Remove gdb workaround from readline/complete.c Tom Tromey
2019-08-06 20:43 ` [PATCH 5/8] Fix gdb's selftest.exp after readline import Tom Tromey
2019-08-13 17:02 ` [committed][gdb/testsuite] Fix gdb.gdb/selftest.exp regexp Tom de Vries
2019-08-06 20:43 ` [PATCH 7/8] Remove readline hack from gdb_select Tom Tromey
2019-08-07 14:29 ` Pedro Alves
2019-08-07 22:03 ` Tom Tromey
2019-08-07 22:16 ` Christian Biesinger via gdb-patches
2019-08-06 20:43 ` [PATCH 3/8] Remove gdb workaround from readline/emacs_keymap.c Tom Tromey
2019-08-07 3:05 ` [PATCH 0/8] Upgrade readline Kevin Buettner
2019-08-07 13:38 ` Tom Tromey
2019-08-07 13:40 ` Tom Tromey
2019-08-14 10:21 ` Tom de Vries
2019-08-15 13:46 ` Tom Tromey
2019-08-19 16:38 ` Tom de Vries
2019-08-07 16:32 ` Sergio Durigan Junior
2019-08-07 19:31 ` Tom Tromey
2019-08-12 19:46 ` Sergio Durigan Junior [this message]
2019-08-12 19:52 ` Christian Biesinger via gdb-patches
2019-08-12 16:57 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k1bi418b.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).