From: Jakub Moc <jakub@gentoo.org>
To: Bret Towe <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] mac/xmms-mac licence issue
Date: Sun, 25 Dec 2005 03:37:04 +0100 [thread overview]
Message-ID: <1699402699.20051225033704@gentoo.org> (raw)
In-Reply-To: <dda83e780512241811m6659a9b4t92948472842dc84c@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]
25.12.2005, 3:11:53, Bret Towe wrote:
> i can understand putting proper warning in the ebuild if the dev thinks
> that its worth the user really noting the issues surrounding it, not
> forcing their ideals onto the user if i wanted that i would run debian
Erm, we are not forcing our ideal on users, we simple refuse to commit an
ebuild for code which has no valid license.
For those unfamiliar with the whole thing (Bug 52882, Bug 94477 and tons of
dupes): Someone has forked a proprietary code with a sucky license,
relicensed it under fake LGPL for the sole purpose of being able to host the
project on SF, and even explicitely acknowledges that what he's doing is
illegal:
--- COPYING ------
Due to the license <License.htm>, so I can't make it public,
Last November, I decided to register mac-port at SourceForge,
so I had to choose an open source license, so I chosen LGPL
for this mac-port. It is close to the original license,
but doesn't get the permission from the original author, Matt.
This license would be changed when the author asks in the
future.
------------------
What the heck kind of license and behaviour is the above? And why should
Gentoo ship such crap?
--
Best regards,
Jakub Moc
mailto:jakub@gentoo.org
GPG signature: http://subkeys.pgp.net:11371/pks/lookup?op=get&search=0xCEBA3D9E
Primary key fingerprint: D2D7 933C 9BA1 C95B 2C95 B30F 8717 D5FD CEBA 3D9E
... still no signature ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 183 bytes --]
next prev parent reply other threads:[~2005-12-25 2:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-25 2:11 [gentoo-dev] mac/xmms-mac licence issue Bret Towe
2005-12-25 2:37 ` Jakub Moc [this message]
2005-12-25 2:51 ` Brian Harring
2005-12-25 3:10 ` Re[2]: " Jakub Moc
2005-12-25 3:22 ` Bret Towe
2005-12-25 3:34 ` Brian Harring
2005-12-25 3:43 ` Bret Towe
2005-12-25 3:02 ` Carsten Lohrke
2005-12-25 3:17 ` Bret Towe
2005-12-25 3:25 ` Ciaran McCreesh
2005-12-25 3:35 ` Bret Towe
2005-12-25 3:42 ` Daniel Ostrow
2005-12-25 3:47 ` Bret Towe
2005-12-25 14:17 ` Luis F. Araujo
2005-12-25 16:04 ` Curtis Napier
2005-12-25 3:28 ` Brian Harring
2005-12-25 3:32 ` Daniel Ostrow
2005-12-25 3:38 ` Bret Towe
2005-12-25 3:49 ` Ciaran McCreesh
2005-12-25 3:32 ` Re[2]: " Jakub Moc
2005-12-25 3:41 ` Dale
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=1699402699.20051225033704@gentoo.org \
--to=jakub@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