From: Francis Laniel <flaniel@linux.microsoft.com>
To: buildroot@buildroot.org
Cc: Francis Laniel <flaniel@linux.microsoft.com>
Subject: [Buildroot] [RFC PATCH v1 0/4] Bump pahole and tbb and remove sysdig
Date: Mon, 17 Jun 2024 16:10:16 +0100 [thread overview]
Message-ID: <20240617151020.31120-1-flaniel@linux.microsoft.com> (raw)
Hi,
With this contribution, I am bumping pahole and tbb to the latest
available versions.
Also, I am removing package related to sysdig: falcosecurity-libs
and sysdig itself.
On this point, I would like to have your opinion, hence the RFC
label.
Maintaining sysdig has been complicated as this software changes
really fast which has impact on the way to build it.
Sadly, I cannot cope with this changes as fast as they arrive to
be able to maintain it in buildroot.
So, rather than having a very outdated package, I think this is
better to remove it.
Francis Laniel (4):
package/pahole: bump to version 1.27
package/tbb: bump to version 2021.12.0.
package/sysdig: remove package.
package/falcosecurity-libs: remove package.
DEVELOPERS | 3 -
package/Config.in | 2 -
...cmake-Permit-setting-GRPC_CPP_PLUGIN.patch | 34 --------
package/falcosecurity-libs/Config.in | 32 --------
.../falcosecurity-libs.hash | 5 --
.../falcosecurity-libs/falcosecurity-libs.mk | 82 -------------------
package/pahole/pahole.hash | 2 +-
package/pahole/pahole.mk | 2 +-
package/sysdig/Config.in | 34 --------
package/sysdig/sysdig.hash | 3 -
package/sysdig/sysdig.mk | 38 ---------
package/tbb/tbb.hash | 2 +-
package/tbb/tbb.mk | 2 +-
13 files changed, 4 insertions(+), 237 deletions(-)
delete mode 100644 package/falcosecurity-libs/0001-cmake-Permit-setting-GRPC_CPP_PLUGIN.patch
delete mode 100644 package/falcosecurity-libs/Config.in
delete mode 100644 package/falcosecurity-libs/falcosecurity-libs.hash
delete mode 100644 package/falcosecurity-libs/falcosecurity-libs.mk
delete mode 100644 package/sysdig/Config.in
delete mode 100644 package/sysdig/sysdig.hash
delete mode 100644 package/sysdig/sysdig.mk
Best regards.
--
2.34.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2024-06-17 15:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 15:10 Francis Laniel [this message]
2024-06-17 15:10 ` [Buildroot] [RFC PATCH v1 1/4] package/pahole: bump to version 1.27 Francis Laniel
2024-07-11 17:58 ` Thomas Petazzoni via buildroot
2024-06-17 15:10 ` [Buildroot] [RFC PATCH v1 2/4] package/tbb: bump to version 2021.12.0 Francis Laniel
2024-07-11 17:58 ` Thomas Petazzoni via buildroot
2024-06-17 15:10 ` [Buildroot] [RFC PATCH v1 3/4] package/sysdig: remove package Francis Laniel
2024-07-11 18:00 ` Thomas Petazzoni via buildroot
2024-07-11 18:08 ` Angelo Compagnucci
2024-06-17 15:10 ` [Buildroot] [RFC PATCH v1 4/4] package/falcosecurity-libs: " Francis Laniel
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=20240617151020.31120-1-flaniel@linux.microsoft.com \
--to=flaniel@linux.microsoft.com \
--cc=buildroot@buildroot.org \
/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