From: Ferris McCormick <fmccor@gentoo.org>
To: Chris White <chriswhite@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Panda 3D licensing issues
Date: Sat, 18 Jun 2005 00:32:10 +0000 (UTC) [thread overview]
Message-ID: <Pine.LNX.4.63.0506180029060.24587@terciopelo.krait.us> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, 18 Jun 2005, Chris White wrote:
> I was given a user submitted ebuild request for the package panda3d.
> However, upon reading the licesnse is it seems that it's one of those
> "sacrifice your newborn child and kill kittens" type licenses.
> Someone mind going over it and verifying I'm not totally lost there:
>
> http://panda3d.org/manual.php?page=license
>
> Thanks,
> Chris White
>
I suppose it's paragraph 4 you object to? It seems to say that if a user
makes changes to Panda and then distributes Panda with these changes, then
(1) the changes must be identified as the user's, not as Panda's, (2) the
user must send these changes to Panda.
For Gentoo, I suppose that means that if Gentoo has to make changes to the
software in order to support it, then Gentoo must identify them as Gentoo
changes and send them to Panda. In Gentoo's case, this seems mostly to
mean that Panda must be told what Gentoo has to do to support Panda.
Or am I missing something?
Regards,
Ferris
- --
Ferris McCormick (P44646, MI) <fmccor@gentoo.org>
Developer, Gentoo Linux (sparc)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCs2uPQa6M3+I///cRAiXNAJ44wlYgPlCwIwMqpbZ4fdZuTLvA6wCgp1wr
joKukJG7XpnHSjDYpVTs6V4=
=8lBI
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2005-06-18 0:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-18 0:32 Ferris McCormick [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-18 7:42 [gentoo-dev] Panda 3D licensing issues Chris White
2005-06-17 23:52 ` Joshua Baergen
2005-06-18 8:12 ` Chris Bainbridge
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=Pine.LNX.4.63.0506180029060.24587@terciopelo.krait.us \
--to=fmccor@gentoo.org \
--cc=chriswhite@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