From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/sysdig: New package
Date: Tue, 17 Mar 2015 13:23:39 +0200 [thread overview]
Message-ID: <20150317112339.GM2415@tarshish> (raw)
In-Reply-To: <1426589808-568-1-git-send-email-angelo.compagnucci@gmail.com>
Hi Angelo,
On Tue, Mar 17, 2015 at 11:56:48AM +0100, Angelo Compagnucci wrote:
> diff --git a/package/sysdig/Config.in b/package/sysdig/Config.in
> new file mode 100644
> index 0000000..94b088f
> --- /dev/null
> +++ b/package/sysdig/Config.in
> @@ -0,0 +1,17 @@
> +comment "sysdig needs a Linux kernel to be built"
> + depends on !BR2_LINUX_KERNEL
> +
> +config BR2_PACKAGE_SYSDIG
> + bool "sysdig"
> + select BR2_PACKAGE_ZLIB
> + select BR2_PACKAGE_LUAJIT
> + select BR2_PACKAGE_LIBJSON
This packages also needs to depend on all the dependencies of these packages.
Please read the whole section under
http://nightly.buildroot.org/manual.html#depends-on-vs-select.
> + depends on BR2_LINUX_KERNEL
> + help
> + Sysdig is open source, system-level exploration:
> + capture system state and activity from a running Linux instance,
> + then save, filter and analyze.
> + Think of it as strace + tcpdump + lsof + awesome sauce.
> + With a little Lua cherry on top.
> +
> + http://sysdig.org
A dependencies comment is still missing here
(http://nightly.buildroot.org/manual.html#_dependencies_on_a_linux_kernel_built_by_buildroot).
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-03-17 11:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 10:56 [Buildroot] [PATCH v2] package/sysdig: New package Angelo Compagnucci
2015-03-17 11:23 ` Baruch Siach [this message]
2015-03-17 11:31 ` Angelo Compagnucci
2015-03-17 11:48 ` Baruch Siach
2015-03-17 11:59 ` Angelo Compagnucci
2015-03-17 13:12 ` Thomas Petazzoni
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=20150317112339.GM2415@tarshish \
--to=baruch@tkos.co.il \
--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.