All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Some legal-info observations/problems
Date: Wed, 9 Oct 2013 09:29:14 +0200	[thread overview]
Message-ID: <20131009092914.6d9ba36c@skate> (raw)
In-Reply-To: <CAHt8ZCNVeoNRPxn0A7CX_NjEdQPh+f42P66=6xJWB-oMU+saHQ@mail.gmail.com>

Dear Simon Dawson,

On Wed, 9 Oct 2013 08:23:27 +0100, Simon Dawson wrote:

> >  Ideally, such an external license should be downloaded already with 'make
> > source'. Though that is perhaps stretching it a little...
> 
> This can now be achieved by using Thomas P's new <pkg>_EXTRA_DOWNLOADS
> mechanism to download the license file(s); I wonder if that would be
> an acceptable idiom in this situation...?

Potential problems:

 * <pkg>_EXTRA_DOWNLOADS downloads from the same <pkg>_SITE that is
   used to download <pkg>_SOURCE. So if your tarball and license files
   are not at the same location, it won't work. This could be fixed by
   having <pkg>_EXTRA_DOWNLOADS use a full path rather than relying on
   <pkg>_SITE.

 * <pkg>_EXTRA_DOWNLOADS = foo will download the file as "foo" in the
   download directory. However, I do expect many of the license files
   that you would download this way to have relatively similar names:
   COPYING, LICENSE, Copyright, or something like that. And therefore,
   if two different packages have <pkg>_EXTRA_DOWNLOADS =
   http://someplace/COPYING, the COPYING files would overwrite each
   other in the download directory.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2013-10-09  7:29 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 [this message]
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
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=20131009092914.6d9ba36c@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.