Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] cutelyst: new package
Date: Tue, 17 Jul 2018 16:08:21 +0200	[thread overview]
Message-ID: <20180717160821.2178aacf@windsurf> (raw)
In-Reply-To: <CACo8zOdPnJhMDqcJMp4fdKdLTsuGg9RLMNbjGEZBtxQaXEOeyg@mail.gmail.com>

Hello,

On Tue, 17 Jul 2018 10:23:26 -0300, Daniel Nicoletti wrote:

> > Why do you have a depends on BR2_PACKAGE_QT5_JSCORE_AVAILABLE ? This
> > dependency is not used by anything in qt5base.  
> I based on the grantlee package, I actually thought this means QJson..

Grantlee has the BR2_PACKAGE_QT5_JSCORE_AVAILABLE dependency because it
selects the BR2_PACKAGE_QT5SCRIPT option.

Since you don't select BR2_PACKAGE_QT5SCRIPT, there is no reason to
depend on BR2_PACKAGE_QT5_JSCORE_AVAILABLE.

> > We like to have a hash for the license file as well.  
> a hash of the license file included in the tarball?

Yes. This allows us to detect when license files are modified, and
therefore to check if the license terms have been changed.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-07-17 14:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-16 20:49 [Buildroot] [PATCH] cutelyst: new package Daniel Nicoletti
2018-07-17  7:01 ` Thomas Petazzoni
2018-07-17 13:23   ` Daniel Nicoletti
2018-07-17 14:08     ` Thomas Petazzoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-07-17 20:46 Daniel Nicoletti
2018-07-18 10:59 ` Thomas Petazzoni
2018-07-18 13:24   ` Daniel Nicoletti
2018-07-18 13:35     ` Thomas Petazzoni
2018-07-18 15:20   ` Thomas Petazzoni
2018-07-19 13:40     ` Daniel Nicoletti

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=20180717160821.2178aacf@windsurf \
    --to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox