Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [Patch v3 1/2] rust-bootstrap: new package
Date: Wed, 19 Oct 2016 08:17:48 +0200	[thread overview]
Message-ID: <20161019061748.GA24316@itchy> (raw)
In-Reply-To: <ee04066a-2251-60d0-78f5-3fd3e0525bf1@mind.be>

On 16-10-19 00:09:30, Arnout Vandecappelle wrote:
>
>
> On 18-10-16 22:47, Eric Le Bihan wrote:
> > Hi!
> >
> > On 16-10-16 13:27:51, Arnout Vandecappelle wrote:
> >>
> >>
> >> On 15-07-16 00:01, Eric Le Bihan wrote:
> [snip]
> >>> +RUST_BOOTSTRAP_LICENSE = Apache-2.0, MIT
> >>
> >>  Can you specify which parts or under which license?
> >
> > Rust is dual licensed (Apache-2.0 OR MIT). So, I'll change it to:
> >
> > RUST_BOOTSTRAP_LICENSE = Dual Apache-2.0/MIT
>
>  No, it should be
>
> RUST_BOOTSTRAP_LICENSE = Apache-2.0 or MIT
>
> See the example in the manual under the generic package infra [1].

Right. I should have read the manual instead of sampling packages.
The following ones currently use "FOO_LICENSE = Dual first/second":

- libsamplerate
- nettle
- freetype

I'll send a patch to make them compliant. Looking at the manual [1], I do
not see what should be used for "proprietary" or "commercial". So, for
libsamplerate, should I use "LIBSAMPLERATE_LICENSE = GPLv2+ or COMMERCIAL"?

[1] https://buildroot.org/downloads/manual/manual.html#legal-info-list-licenses

Best regards,

--
ELB

  reply	other threads:[~2016-10-19  6:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-14 22:01 [Buildroot] [Patch v3 0/2] Add support for the Rust programming language Eric Le Bihan
2016-07-14 22:01 ` [Buildroot] [Patch v3 1/2] rust-bootstrap: new package Eric Le Bihan
2016-10-16 11:27   ` Arnout Vandecappelle
2016-10-18 20:47     ` Eric Le Bihan
2016-10-18 22:09       ` Arnout Vandecappelle
2016-10-19  6:17         ` Eric Le Bihan [this message]
2016-07-14 22:01 ` [Buildroot] [Patch v3 2/2] rust: " Eric Le Bihan
2016-10-16 15:28   ` Arnout Vandecappelle

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=20161019061748.GA24316@itchy \
    --to=eric.le.bihan.dev@free.fr \
    --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