Re: [Buildroot] [PATCH v2] package/slirp4netns: new package

[Thomas Petazzoni via buildroot <buildroot@buildroot.org>]

On Mon, 29 Aug 2022 21:48:28 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> Yes, the idea is that, by submitting a package, you show an interest in
> having that package work flawlessly in Buildroot.
> 
> Listing the package in DEVELOPERS will ensure that you are copied on the
> build failures about that package, that the autobuilders [0] may uncover
> when running the random configurations.
> 
> It also ensures that, should someone submit a change to that package,
> you get listed by the utils/get-developers script, so they would put you
> on Cc to the change, on the assumption that you know (at least a bit)
> about the package.

And also, by being in the DEVELOPERS, you get notified by e-mail when:

 - The upstream project corresponding to your package makes a new
   release, hinting you that you should perhaps update the Buildroot
   package. This works fine if the corresponding project is known by
   release-monitoring.org, and release-monitoring.org has a mapping
   between the Buildroot name and the name of the project as known by
   release-monitoring.org.

 - There is a CVE (security vulnerability) reported on the upstream
   project. This works fine is the CPE variables in your package are
   correctly defined.

Best regards,

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