Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: dje@google.com
Cc: uweigand@de.ibm.com, drow@false.org, gdb-patches@sourceware.org
Subject: Re: Per-type architecture (Re: [10/15] Basic value access routines)
Date: Tue, 23 Jun 2009 16:42:00 -0000	[thread overview]
Message-ID: <200906231642.n5NGg6S9014370@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <e394668d0906230855g86466bcj62893515407641be@mail.gmail.com> 	(message from Doug Evans on Tue, 23 Jun 2009 08:55:39 -0700)

> Date: Tue, 23 Jun 2009 08:55:39 -0700
> From: Doug Evans <dje@google.com>
> 
> On Mon, Jun 22, 2009 at 5:41 PM, Ulrich Weigand<uweigand@de.ibm.com> wrote:
> > In fact, if it weren't that we want to avoid excessive
> > dependencies on XML libraries, I'd argue we should just parse XML
> > into a standard DOM tree representation as provided by those.
> >
> > Looking at this this way, serialization/deserialization of XML into and out
> > of those "DOM tree" structures *should not* involve too much GDB specifics
> > like GDB private data structures, but simply follow the self-describing
> > property of the XML format ...
> 
> OOC, what "excessive dependencies" are you referring to?
> It seems odd to want to avoid dependencies on libraries, libraries are good.
> [I'm sure there's more to the story here, hence the question.  :-)]

Some people think that a basic UNIX-like system should include the
tools to build and debug computer programs, at least those written in
C.  So on OpenBSD (and most of the other BSD's) we ship gcc, binutils
and gdb as part of the base operating system.  This means that if
these tools depend on certain libraries, we have to include those
libraries as well.  There are a couple of issues here:

* We think we should not ship any libraries that have a license that
  is more restrictive than the BSD license.

* We think we should only ship "standard" libraries since shipping
  "non-standard" libraries encourages people to write programs that
  are non-portable.

* We think that we should only ship libraries that meet certain
  minimal quality standards, especially with respect to security.

Another perhaps less OpenBSD-specific argument is that I think it
should be possible for people to compile software themselves.  This
sort of breaks down if before being able to compile that software I
first need to install a dozen of libtraries, especially if those
libraries themseleves have dependencies.


  reply	other threads:[~2009-06-23 16:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 15:20 [10/15] Basic value access routines Ulrich Weigand
2009-06-15 16:35 ` Doug Evans
2009-06-15 16:59   ` Ulrich Weigand
2009-06-22 20:32     ` Per-type architecture (Re: [10/15] Basic value access routines) Ulrich Weigand
2009-06-22 20:59       ` Daniel Jacobowitz
2009-06-23  0:41         ` Ulrich Weigand
2009-06-23 13:49           ` Daniel Jacobowitz
2009-06-23 14:02             ` Pedro Alves
2009-06-23 17:06             ` Ulrich Weigand
2009-06-23 17:30               ` Daniel Jacobowitz
2009-06-23 15:55           ` Doug Evans
2009-06-23 16:42             ` Mark Kettenis [this message]
2009-06-23 16:53               ` Daniel Jacobowitz
2009-06-23 16:57             ` Ulrich Weigand
2009-06-23 17:36               ` Doug Evans
2009-06-24 15:31     ` [10/15] Basic value access routines Tom Tromey
2009-06-24 15:46       ` Daniel Jacobowitz
2009-06-24 16:26         ` Doug Evans
2009-06-24 19:41           ` 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=200906231642.n5NGg6S9014370@brahms.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=dje@google.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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