All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] libbson: new package
Date: Mon, 10 Apr 2017 13:53:53 +0200	[thread overview]
Message-ID: <1df728ce-3c14-a9d8-2f11-cbe837a90e38@mind.be> (raw)
In-Reply-To: <1491587714.491322104@f30.my.com>

 Hi Semyon,

 Please keep the list in Cc. Your questions and answers may be relevant to other
people as well, and you may get faster answers from someone else.


On 07-04-17 19:55, semenak94 at mail.ru wrote:
> Thanks for such detailed answer and  your patience! I'm still a newcomer in
> buildroot community and it's my first experience in open source.

 We aim to please :-) (though sometimes we miss :-P )


> And I have some question : how correctly set all licenses of package, except
> watching license file? I'm not experienced in it... 

 It's unfortunately not so easy. Many packages reuse source code from somewhere
else, so you really have to look at every file to check the license. Fortunately
there are tools that can help:

- the 'licensecheck' script in Debian/Ubuntu;
- fossology, which has an online version at https://fossology.ist.unomaha.edu/

 However, some files in the source code are not used at all (e.g.
windows-specific sources), or don't end up in the target (e.g. the build
scripts), and these shouldn't be included in the license statement.

 For packages that have a Debian equivalent, it's also a good idea to look at
the copyright declaration in Debian, but sometimes their binary packages are
split up differently which can make it tricky to get it right.

> Does license in buildroot
> have any more value,  than formal signature?

 Not sure what you mean here. The license specification helps people to
understand which licenses they have to comply with when they use the result of
the Buildroot build. If with "formal signature" you mean the Signed-off-by, that
only says something about compliance with the license of Buildroot itself, it
has nothing to do with packages.

 Regards,
 Arnout

> 
> Thanks a lot and sorry for stupid questions.
[snip]

-- 
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:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  parent reply	other threads:[~2017-04-10 11:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <libbson: new package>
2017-04-07 11:42 ` [Buildroot] [PATCH] libbson: new package Semyon Kolganov
2017-04-07 12:01   ` Arnout Vandecappelle
2017-04-07 12:18 ` [Buildroot] [PATCHv2] " Semyon Kolganov
2017-04-07 17:23   ` Arnout Vandecappelle
     [not found]     ` <1491587714.491322104@f30.my.com>
2017-04-10 11:53       ` Arnout Vandecappelle [this message]
2017-04-10 11:16 ` [Buildroot] [PATCHv3] " Semyon Kolganov
2017-04-10 13:52   ` Arnout Vandecappelle
2017-04-10 14:29 ` [Buildroot] [PATCHv4] " Semyon Kolganov
2017-04-10 14:59   ` 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=1df728ce-3c14-a9d8-2f11-cbe837a90e38@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 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.