From: Stuart Ballard <stuart.a.ballard@gmail.com>
To: David Gilbert <david.gilbert@object-refinery.com>
Cc: GNU Classpath <classpath@gnu.org>, mauve-discuss@sourceware.org
Subject: Re: Mauve license
Date: Thu, 16 Feb 2006 17:34:00 -0000 [thread overview]
Message-ID: <ba76afd90602160934r21a0af33w63b5b9fe99704cb@mail.gmail.com> (raw)
In-Reply-To: <43F4AB1C.3000705@object-refinery.com>
On 2/16/06, David Gilbert <david.gilbert@object-refinery.com> wrote:
> Free to use, free to redistribute, and since you'll never want to
> combine Mauve with anything else, I can't see why the GPL is considered
> a showstopper.
Politics don't have to make sense ;)
The logical conclusion of your statements, though, is that the GPL
isn't actually making any practical difference. And if that's the
case, what's the point of using it?
> I think a more significant "problem" is practical: Mauve, which
> predates JUnit, uses its own test harness and Harmony is using JUnit.
> Integrating the two is a pile of work that you're not going to find
> anyone willing to spend time on. I think we should just accept that
> there are going to be two separate test suites, that will overlap in
> some places. It's not that big a deal in the scheme of things.
AIUI currently you couldn't integrate the two if you wanted to because
JUnit is under a non-GPL-compatible license. Another reason why a
Mauve license change would be a benefit.
From a practical point of view, if the license issues disappeared, it
would presumably be easy enough to create a "junit" directory in
mauve, have the mauve launcher scripts run both junit *and* the
existing harness, pull the harmony tests into the new folder,
everybody write new tests as junit tests, and gradually convert the
old tests one-at-a-time over time. It wouldn't have to be a once-off
"convert the world" operation.
> We have those tests now, just in separate places.
True. The current situation isn't a disaster. It would just be nice to
get some cooperation in a place where, IMO, it clearly *does* make
sense and the showstoppers seem to be entirely unnecessary.
Stuart.
--
http://sab39.dev.netreach.com/
next prev parent reply other threads:[~2006-02-16 17:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-16 15:55 Stuart Ballard
2006-02-16 16:17 ` Mauve license: How with COST.OMG.ORG? Audrius Meskauskas
2006-02-16 16:41 ` Mauve license David Gilbert
2006-02-16 17:34 ` Stuart Ballard [this message]
2006-02-16 16:52 ` Andrew Haley
2006-02-16 17:14 ` Archie Cobbs
2006-02-16 17:25 ` Stuart Ballard
2006-02-16 17:35 ` Andrew Haley
2006-02-16 17:40 ` Archie Cobbs
2006-02-16 17:51 ` Stuart Ballard
2006-02-16 17:59 ` Andrew Haley
2006-02-16 18:01 ` Archie Cobbs
2006-02-16 18:19 ` Stuart Ballard
2006-02-16 18:00 ` Robert Schuster
2006-02-21 0:09 ` 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=ba76afd90602160934r21a0af33w63b5b9fe99704cb@mail.gmail.com \
--to=stuart.a.ballard@gmail.com \
--cc=classpath@gnu.org \
--cc=david.gilbert@object-refinery.com \
--cc=mauve-discuss@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).