From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Some legal-info observations/problems
Date: Wed, 09 Oct 2013 18:46:29 +0200 [thread overview]
Message-ID: <52558865.8070804@mind.be> (raw)
In-Reply-To: <525556CE.3000308@lucaceresoli.net>
On 10/09/13 15:14, Luca Ceresoli wrote:
>> Related to this is the question of a license URL. I personally think
>> it is not legally safe to only refer to a URL from a package, because
>> who knows someone changes the license text on the URL. They could just
>> alter the license of existing sources.
>> So although the feature of automatically downloading a license text
>> from its URL looks nice, I (not a lawyer) would not recommend
>> implementing it. I follow ThomasP's reasoning of requesting upstream
>> to add the effective license text to the sources, and in the meantime
>> using the magic value decided above for case (b).
>
> I agree with you. Regarding the legal stuff we should stay on the safe
> side. But Arnout and Simon expressed an opposite opinion on another
> branch of this thread...
If the package specifies that the license is available at a specific
URL, then that is the license, right? It is true that the license may
change unexpectedly, but to make sure it stays consistent we should
download the license at the same time that the source is downloaded
(which could be tricky, I admit).
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-10-09 16:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 14:06 [Buildroot] Some legal-info observations/problems Thomas De Schampheleire
2013-10-02 14:22 ` Peter Korsgaard
2013-10-02 14:32 ` Thomas De Schampheleire
2013-10-02 15:23 ` Thomas Petazzoni
2013-10-02 16:33 ` Luca Ceresoli
2013-10-03 8:24 ` Thomas De Schampheleire
2013-10-03 16:40 ` Arnout Vandecappelle
2013-10-04 8:54 ` Thomas De Schampheleire
2013-10-04 9:07 ` Thomas Petazzoni
2013-10-04 15:30 ` Ryan Barnett
2013-10-04 15:34 ` Thomas Petazzoni
2013-10-04 15:39 ` Ryan Barnett
2013-10-04 15:46 ` Simon Dawson
2013-10-07 22:43 ` Arnout Vandecappelle
2013-10-09 7:23 ` Simon Dawson
2013-10-09 7:29 ` Thomas Petazzoni
2013-10-09 7:31 ` Simon Dawson
2013-10-05 21:07 ` Luca Ceresoli
2013-10-02 16:31 ` Arnout Vandecappelle
2013-10-03 8:30 ` Thomas De Schampheleire
2013-10-02 18:49 ` Ryan Barnett
2013-10-03 8:34 ` Thomas De Schampheleire
2013-10-03 13:31 ` Ryan Barnett
2013-10-03 13:42 ` Danomi Manchego
2013-10-03 14:12 ` Ryan Barnett
2013-10-03 16:50 ` Arnout Vandecappelle
2013-10-03 21:38 ` Peter Korsgaard
2013-10-03 22:44 ` Ryan Barnett
2013-10-07 8:19 ` Thomas De Schampheleire
2013-10-09 13:14 ` Luca Ceresoli
2013-10-09 16:46 ` Arnout Vandecappelle [this message]
2013-10-11 14:13 ` Thomas De Schampheleire
2013-10-09 19:54 ` Ryan Barnett
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=52558865.8070804@mind.be \
--to=arnout@mind.be \
--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