Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: palves@redhat.com, gdb-patches@sourceware.org
Subject: Re: Move gdbsupport to the top level
Date: Tue, 17 Sep 2019 16:16:00 -0000	[thread overview]
Message-ID: <83tv9avqxx.fsf@gnu.org> (raw)
In-Reply-To: <8736guzyv8.fsf@tromey.com> (message from Tom Tromey on Tue, 17	Sep 2019 10:11:39 -0600)

> From: Tom Tromey <tom@tromey.com>
> Cc: Pedro Alves <palves@redhat.com>,  gdb-patches@sourceware.org
> Date: Tue, 17 Sep 2019 10:11:39 -0600
> 
> We discussed this at Cauldron and agreed to try this approach.

Is it possible to still discuss this?  Or is the decision at Cauldron
final and cannot be appealed?

> That is, the plan is to remove the readline sources from the tree,
> and remove --with-system-readline, but follow the approach of some
> other libraries where one can unpack readline into the source tree
> and top-level configure will arrange to build it.

Would it be possible for whoever tars the release to drop the readline
into the tree and build it under some opt-in configure-time switch?
Making this opt-in might solve at least some of the problems that led
to the decision, I think/hope.


  reply	other threads:[~2019-09-17 16:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-11 21:03 Tom Tromey
2019-07-12  7:18 ` Andrew Pinski
2019-07-12 13:05   ` Tom Tromey
2019-07-15 20:10 ` Tom Tromey
2019-08-20 19:38 ` Pedro Alves
2019-08-20 20:22   ` Tom Tromey
2019-09-17 16:11     ` Tom Tromey
2019-09-17 16:16       ` Eli Zaretskii [this message]
2019-09-17 16:35         ` Tom Tromey
2019-09-17 16:45           ` Eli Zaretskii

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=83tv9avqxx.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --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