From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot and GPL compliance
Date: Fri, 6 Jan 2012 08:25:57 -0600 [thread overview]
Message-ID: <201201060826.00086.minimod@morethan.org> (raw)
In-Reply-To: <201201060210.03701.vapier@gentoo.org>
On Fri January 6 2012, Mike Frysinger wrote:
> On Wednesday 14 December 2011 02:40:54 Thomas De Schampheleire wrote:
> > * What about the tarballs? Should the tarballs themselves be included
> > in the distribution, or would they be downloaded from the web by the
> > user running buildroot? I think it is safer to include the tarballs,
> > since you never know whether the official location will continue to
> > exist in the future (or be temporarily out-of-order, as with
> > kernel.org)
>
> it would be simplest for people distributing binaries upon request, but if
> they provide URLs and they're available, that should be satisfactory.
>
> > * How to handle proprietary applications? Even though during
> > development these applications may be build from within buildroot
> > (when sources are available), one would typically not want to
> > distribute the sources to the end-user. Still, in order to be able to
> > regenerate the system, I think the user should have access to the
> > binary versions of these applications. How do we handle this, what isorg
> > the best practice?
>
> there's no legal requirement that people distributing binaries make this easy.
>
I can't think of any that include the words: "practical' let alone "easy".
;-)
> > Other discussion points are welcome.
>
> what might be cool is adding a target that produces a tarball of everything
> that we expect would be required for license compliance. should be somewhat
> easy to automate.
>
I see this often in actual practice for the case of Media Player firmware.
These firmware packages are often a mix of open source and closed source.
The builders put a '.gnu' (or similar) tag file in each directory they want
included in their source reference tar-ball.
Some also write a manifest file listing open/closed status of each package.
Noticed only because at least some of these people doing the scripting do not
exclude the '.gnu' or '.gnulock' tag file from the tar-ball. ;-)
Mike
> -mike
>
prev parent reply other threads:[~2012-01-06 14:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 7:40 [Buildroot] Buildroot and GPL compliance Thomas De Schampheleire
2011-12-18 12:31 ` Stephan Hoffmann
2011-12-19 21:08 ` Luca Ceresoli
2011-12-19 21:02 ` Luca Ceresoli
2012-01-06 7:10 ` Mike Frysinger
2012-01-06 14:25 ` Michael S. Zick [this message]
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=201201060826.00086.minimod@morethan.org \
--to=minimod@morethan.org \
--cc=buildroot@busybox.net \
/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