From: Todd Goodman <tsg@bonedaddy.net>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] Licence compliance - capturing all source files used to make a build?
Date: Sat, 3 Mar 2012 18:42:27 -0500 [thread overview]
Message-ID: <20120303234227.GB30374@ns1.bonedaddy.net> (raw)
In-Reply-To: <4F526136.80604@wildgooses.com>
* Ed W <lists@wildgooses.com> [120303 13:29]:
> Hi
>
[..]
> >> My understanding is that for a GPL licence one should provide a
> >> copy of these patches in the "code dump", not just an http link?
> >> Is that your understanding?
> > I think your understanding is incomplete, and I recommend that you
> > read through the license again.
>
> ?? Why all the stupid hints rather than just stating the answer!
I'm sure it's just frustration but your emails really make you sound
like an a-hole with a sense of entitlement.
They're legal licenses. As with anything involved with lawyers and the
legal system you really need to decide for yourself what needs to be
done (most people to be safe would contact a lawyer.)
If you're at a company releasing a product then the company most likely
has a legal dept or legal consultant. They certainly would here in the
US (I know you said you're not in the US so perhaps that's not the
case.)
Have you looked at http://www.gnu.org/licenses/gpl-faq.html?
I'm not a lawyer (by a far shot) but what's the problem with creating a
script that when run pulls the upstream files from
/usr/portage/distfiles, the files and ebuilds from /usr/portage for
whatever packages you have installed on whatever you're releasing?
If I were releasing commercial software I'd want all that on a local
mirror (in source control too) so that I could recreate any released
versions.
Todd
next prev parent reply other threads:[~2012-03-04 0:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 14:46 [gentoo-embedded] Licence compliance - capturing all source files used to make a build? Ed W
2012-02-29 17:39 ` Peter Stuge
2012-03-01 0:36 ` Ed W
2012-03-01 3:36 ` Peter Stuge
2012-03-01 8:20 ` Ed W
2012-03-01 14:53 ` Peter Stuge
2012-03-01 18:57 ` Ed W
2012-03-01 19:05 ` Peter Stuge
2012-03-03 18:21 ` Ed W
2012-03-03 23:42 ` Todd Goodman [this message]
2012-03-05 20:08 ` Ed W
2012-03-04 5:12 ` Mike Frysinger
2012-03-01 16:18 ` wireless
2012-03-01 16:27 ` Peter Stuge
2012-03-02 6:37 ` Mike Frysinger
2012-03-02 14:35 ` Peter Stuge
2012-03-02 15:22 ` Bertrand Jacquin
2012-03-03 18:34 ` Ed W
2012-03-03 19:00 ` Ed W
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=20120303234227.GB30374@ns1.bonedaddy.net \
--to=tsg@bonedaddy.net \
--cc=gentoo-embedded@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