Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: cgf-gdb-patches@sourceware.org
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Add expat to the GDB sources
Date: Mon, 24 Jul 2006 21:58:00 -0000	[thread overview]
Message-ID: <200607242157.k6OLvqei026186@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20060724163700.GB17430@trixie.casa.cgf.cx> (message from 	Christopher Faylor on Mon, 24 Jul 2006 12:37:00 -0400)

> Date: Mon, 24 Jul 2006 12:37:00 -0400
> From: Christopher Faylor <cgf-gdb-patches@sourceware.org>
> 
> On Mon, Jul 24, 2006 at 11:49:59AM -0400, Daniel Jacobowitz wrote:
> >On Mon, Jul 24, 2006 at 11:30:17AM -0400, Christopher Faylor wrote:
> >>You can make similar statements about any of the libraries which gdb
> >>uses, like ncurses or glibc.  And, you can flip it around, too.
> >>Distros are apt to fix bugs when they are detected.  Are we going to
> >>have someone scanning bugtraq, the expat web site, and the
> >>Fedora/Gentoo/Ubuntu/Debian web sites looking for updates?
> >
> >For the record, Debian has a strict policy against this sort of
> >inclusion.  We already do not use the readline shipped with GDB.  I do
> >not plan to use GDB's expat, either, if it ends up included.
> 
> Huh.  Interesting.  Good for Debian.

We do something similar on OpenBSD.  For us this works pretty well,
because we ship both gdb and readline as part of the base system,
where we have complete control over the version of gdb and readline
that we ship, and do a lot of testing for the specific test setup
chosen.  That's a completely different situation from shipping a
.tar.gz on ftp.gnu.org that people will try to build on a very wide
variety of systems out there.


  reply	other threads:[~2006-07-24 21:58 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-18 13:40 Daniel Jacobowitz
2006-07-18 13:57 ` Daniel Jacobowitz
2006-07-21  0:35   ` Joel Brobecker
2006-07-21  0:39     ` Daniel Jacobowitz
2006-07-21  0:45       ` Joel Brobecker
2006-07-23 21:52   ` Mark Kettenis
2006-07-23 22:03     ` Daniel Jacobowitz
2006-07-23 22:40 ` Christopher Faylor
2006-07-23 22:57   ` Daniel Jacobowitz
2006-07-23 23:13     ` Christopher Faylor
2006-07-24  0:17       ` Daniel Jacobowitz
2006-07-23 23:15     ` Pedro Alves
2006-07-23 23:18   ` Mark Kettenis
2006-07-24  0:15     ` Daniel Jacobowitz
2006-07-24  6:20     ` Joel Brobecker
2006-07-24 15:30       ` Christopher Faylor
2006-07-24 15:50         ` Daniel Jacobowitz
2006-07-24 16:37           ` Christopher Faylor
2006-07-24 21:58             ` Mark Kettenis [this message]
2006-07-24 19:50           ` Eli Zaretskii
2006-07-24 19:52             ` Daniel Jacobowitz
2006-07-24 20:29               ` Eli Zaretskii
2006-07-24 20:36                 ` Daniel Jacobowitz
2006-07-24 15:24     ` Christopher Faylor
2006-07-24 19:47       ` Eli Zaretskii
2006-07-24 19:51         ` Daniel Jacobowitz
2006-07-24 20:22           ` Christopher Faylor
2006-07-24 20:29           ` Eli Zaretskii
2006-07-24 20:43             ` Daniel Jacobowitz
2006-07-24 21:42             ` Christopher Faylor
2006-07-24 22:18               ` DJ Delorie
2006-07-24 22:29               ` Mark Kettenis
2006-07-24 22:34                 ` Daniel Jacobowitz
2006-07-24 22:37                   ` Daniel Jacobowitz
2006-07-25  0:36                     ` Christopher Faylor
2006-07-24 22:49                   ` Mark Kettenis
2006-07-24 23:41                     ` Daniel Jacobowitz
2006-07-25  0:47                 ` Christopher Faylor
2006-07-31 17:33                 ` Daniel Jacobowitz
2006-07-31 20:24                   ` Daniel Jacobowitz
2006-07-31 20:39                     ` Christopher Faylor
2006-07-31 21:33                     ` Mark Kettenis
2006-08-01  0:42                       ` Daniel Jacobowitz
2006-08-01  1:01                         ` Daniel Jacobowitz
2006-07-24 22:08       ` Mark Kettenis

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=200607242157.k6OLvqei026186@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=cgf-gdb-patches@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    /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