From: "Tony \"Chainsaw\" Vroon" <chainsaw@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Adding Nipper license to the tree
Date: Sun, 14 Jun 2009 23:07:05 +0100 [thread overview]
Message-ID: <1245017225.3729.6.camel@localhost> (raw)
In-Reply-To: <4A355D68.6050803@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 564 bytes --]
On Sun, 2009-06-14 at 21:28 +0100, Mike Auty wrote:
> but I thought I should ask what
> the best course of action would be here?
If it were my ebuild, I would not add the updates under the new,
draconic license and either fork the GPL'd code or mask the package for
removal.
You can not in any way guarantee that a Gentoo user is non-commercial.
Especially the patch clause would make ebuilds unsustainable.
As you say the author personally, perhaps there is a sense of reason
that you could appeal to.
> Thanks,
> Mike 5:)
Regards.
Tony V.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-06-14 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 20:28 [gentoo-dev] Adding Nipper license to the tree Mike Auty
2009-06-14 22:07 ` Tony "Chainsaw" Vroon [this message]
2009-06-15 0:39 ` Robin H. Johnson
2009-06-15 23:58 ` Mike Auty
2009-06-16 0:18 ` Tony "Chainsaw" Vroon
2009-06-16 2:04 ` [gentoo-dev] " Duncan
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=1245017225.3729.6.camel@localhost \
--to=chainsaw@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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