Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFC] Add expat to the GDB sources
Date: Mon, 24 Jul 2006 22:18:00 -0000	[thread overview]
Message-ID: <200607242218.k6OMI6ZB001867@greed.delorie.com> (raw)
In-Reply-To: <20060724214157.GC25632@trixie.casa.cgf.cx> (message from 	Christopher Faylor on Mon, 24 Jul 2006 17:41:57 -0400)


> AFAIK, the master for libbfd and libopcodes is in 'src'.  I think DJ
> keeps libiberty in sync so that if you make a change to 'src' it also
> shows up in 'gcc' and vice versa.

FYI if you put it in src only, it vanishes.  It's strictly gcc->src.

> It sounds like you're advocating that every project which relies on
> external libraries should include the source code for those libraries.

As another point of view, what one of the other projects I'm on does
is (1) not include the libraries in the cvs tree, but (2) include a
copy of the latest official sources in the CD-ROMs we distribute.  The
installer knows you need them, but uses the installed ones if they're
available.  If not, a project-private copy is installed and used
instead.  Or, you can use the cd-rom copy to install a shared copy on
your system.

It's a balancing act between "don't screw the user by making it hard
to install" and "don't screw the user by installing bad copies of
common software".


  reply	other threads:[~2006-07-24 22:18 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
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 [this message]
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=200607242218.k6OMI6ZB001867@greed.delorie.com \
    --to=dj@redhat.com \
    --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