From: Sam Barnett-Cormack <sdb@geekworld.co.uk>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Unified device model
Date: Sun, 09 Apr 2006 16:28:04 +0100 [thread overview]
Message-ID: <44392804.6090900@geekworld.co.uk> (raw)
In-Reply-To: <200604091621.45594.paul@codesourcery.com>
Paul Brook wrote:
> I don't buy that. We either share the same drivers (in which case keeping the
> two in sync is trivial) or we don't. All of the systems under consideration
> are [L]GPL licences. We can easily copy the source, so I don't think being
> able to copy bits of binary goo gains us anything.
In my experience of writing multiple systems that do the same thing,
some shared library code (be it static or dynamic (shared object) in
form) makes life much simpler. It can be maintained as a seperate source
module, libtool-ized, and made into a nice bit of magic that just needs
to be modified once, without manually copying-and-pasting bits back and
forth. If it's done statically, it can still be distributed with each
source package to ensure compatibility.
Sam
next prev parent reply other threads:[~2006-04-09 15:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-08 19:57 [Qemu-devel] Unified device model Stanislav Shwartsman
2006-04-08 19:12 ` Jim C. Brown
2006-04-08 19:17 ` Johannes Schindelin
2006-04-08 19:27 ` Leonardo E. Reiter
2006-04-09 6:29 ` Stanislav Shwartsman
2006-04-08 19:28 ` Jim C. Brown
2006-04-09 6:26 ` Stanislav Shwartsman
2006-04-09 10:38 ` Paul Brook
2006-04-09 14:55 ` Jim C. Brown
2006-04-09 15:21 ` Paul Brook
2006-04-09 15:28 ` Sam Barnett-Cormack [this message]
2006-04-09 16:08 ` Jim C. Brown
2006-04-09 19:56 ` Stanislav Shwartsman
2006-04-09 21:02 ` Fabrice Bellard
2006-04-09 15:10 ` Jim C. Brown
[not found] <1b33de610604170003q43b6c453ub94d77b1a10ed43b@mail.gmail.com>
2006-04-17 7:09 ` pete sullivan
-- strict thread matches above, loose matches on Subject: below --
2006-04-23 21:03 Einar Larsson
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=44392804.6090900@geekworld.co.uk \
--to=sdb@geekworld.co.uk \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).