From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Francois Perrad <francois.perrad@gadz.org>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH v2 2/2] package/lynis: new package
Date: Sat, 26 Oct 2024 23:14:08 +0200 [thread overview]
Message-ID: <20241026231408.1690b774@windsurf> (raw)
In-Reply-To: <20240920181212.3572055-3-francois.perrad@gadz.org>
Hello François,
On Fri, 20 Sep 2024 20:12:12 +0200
Francois Perrad <francois.perrad@gadz.org> wrote:
> diff --git a/package/lynis/Config.in b/package/lynis/Config.in
> new file mode 100644
> index 000000000..3f64bc2e1
> --- /dev/null
> +++ b/package/lynis/Config.in
> @@ -0,0 +1,11 @@
> +config BR2_PACKAGE_LYNIS
> + bool "lynis"
> + select BR2_PACKAGE_BUSYBOX_SHOW_OTHERS
> + select BR2_PACKAGE_COREUTILS # runtime (stat)
The "stat" from Busybox cannot be used?
> + def test_run(self):
> + self.login()
> + self.assertRunOk("lynis show version", timeout=90)
Is this a useful enough test? Does it check that runtime dependencies
are present and working?
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-10-26 21:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 18:12 [Buildroot] [PATCH v2 0/2] lynis Francois Perrad
2024-09-20 18:12 ` [Buildroot] [PATCH v2 1/2] package/busybox: handle LIBFOO_BUSYBOX_CONFIG_FIXUPS Francois Perrad
2024-10-07 14:53 ` Adam Duskett
2024-10-07 14:54 ` Adam Duskett
2024-09-20 18:12 ` [Buildroot] [PATCH v2 2/2] package/lynis: new package Francois Perrad
2024-10-26 21:14 ` Thomas Petazzoni via buildroot [this message]
2024-10-27 10:28 ` François Perrad
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=20241026231408.1690b774@windsurf \
--to=buildroot@buildroot.org \
--cc=buildroot@busybox.net \
--cc=francois.perrad@gadz.org \
--cc=thomas.petazzoni@bootlin.com \
/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.