Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Francis Laniel <flaniel@linux.microsoft.com>
Cc: Angelo Compagnucci <angelo@amarulasolutions.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [RFC PATCH v1 3/4] package/sysdig: remove package.
Date: Thu, 11 Jul 2024 20:00:29 +0200	[thread overview]
Message-ID: <20240711200029.0763fc1d@windsurf> (raw)
In-Reply-To: <20240617151020.31120-4-flaniel@linux.microsoft.com>

Hello Francis,

I'm adding in Cc: Angelo who is also listed as a maintainer for this
package in our DEVELOPERS file. Angelo, any feedback?

See below.

On Mon, 17 Jun 2024 16:10:19 +0100
Francis Laniel <flaniel@linux.microsoft.com> wrote:

> Building sysdig within buildroot is a complicated task which
> has changed at each of their release.

But the package is working right now, isn't it? Did you try to update
it to a newer version and encountered some specific issues? If so,
which issues?

Maybe those issues should be communicated back to upstream, so that
they can improve how sysdig is provided/delivered? If something like
Buildroot can't package sysdig, maybe they will be interested in
hearing why?

> As the package seems to not be really used in buildroot, it
> seems wise to remove it.

How can you say it is "not really used"? We have no usage metrics for
packages, so really we have no idea of who uses sysdig.

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

  reply	other threads:[~2024-07-11 18:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-17 15:10 [Buildroot] [RFC PATCH v1 0/4] Bump pahole and tbb and remove sysdig Francis Laniel
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 [this message]
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=20240711200029.0763fc1d@windsurf \
    --to=buildroot@buildroot.org \
    --cc=angelo@amarulasolutions.com \
    --cc=flaniel@linux.microsoft.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox