From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] cukinia: new package
Date: Mon, 1 May 2017 10:51:18 +0200 [thread overview]
Message-ID: <20170501105118.5ce1b97f@free-electrons.com> (raw)
In-Reply-To: <20170425135814.8787-1-alexandre.leblanc@savoirfairelinux.com>
Hello,
On Tue, 25 Apr 2017 09:58:14 -0400, Alexandre Leblanc wrote:
> Cukinia is designed to help Linux-based embedded firmware developers
> run simple validation tests on their firmware. For basic usage it
> requires no dependencies other than busybox.
>
> Cukinia can run tests at boot time which is why we are using SZZcukinia
> since it would possibly be the last script to be executed in 'init.d'.
>
> Signed-off-by: Alexandre Leblanc <alexandre.leblanc@savoirfairelinux.com>
As much as I like adding new package in Buildroot, this project feels
like your own project, very recently started, with no outside
contributions. In the end it's just a single shell script providing a
few functions. Could be useful, but I'm not sure we want to add this as
a Buildroot package that quickly.
Perhaps we need to see if there is some interest/adoption first?
> package/cukinia/Config.in | 12 ++++++++++++
> package/cukinia/SZZcukinia | 7 +++++++
I'm not sure I like this idea of SZZcukinia, though indeed S99 wouldn't
work because a few other Buildroot services are started at S99, and you
want to be after those services. Maybe other developers will have some
ideas?
> +CUKINIA_LICENSE = Apache-2.0 or GPLv3
GPLv3 should be GPL-3.0.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-01 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 13:58 [Buildroot] [PATCH] cukinia: new package Alexandre Leblanc
2017-05-01 8:51 ` Thomas Petazzoni [this message]
2017-05-01 14:48 ` Alexandre Leblanc
2017-05-04 9:16 ` Thomas Petazzoni
2020-04-26 19:56 ` Angelo Compagnucci
2020-04-27 8:08 ` Shyam Saini
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=20170501105118.5ce1b97f@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox