On Sat, 20 Jul 2019 at 00:21:10 +0200, Christoph Biedl wrote:
> The build system of the file package uses autoconf to check for
> presence of the seccomp library and will just disable that feature if
> support is missing. But just adding "libseccomp-dev" will break the
> build on e.g. alpha for an
On Jul 20, Christoph Biedl wrote:
> * Centralize the list of supported archs in the seccomp packages. By
> either creating an empty libseccomp-dev for the archs where seccomp
> is not supported, or by creating a "libseccomp-dev-dummy" for these.
> In the latter case package maintainers woul
On Sat, 20 Jul 2019 00:21:10 +0200, Christoph Biedl wrote:
> * Centralize the list of supported archs in the seccomp packages. By
> either creating an empty libseccomp-dev for the archs where seccomp
> is not supported, or by creating a "libseccomp-dev-dummy" for these.
> In the latter case
Christoph Biedl writes:
> * Centralize the list of supported archs in the seccomp packages. By
> either creating an empty libseccomp-dev for the archs where seccomp
> is not supported, or by creating a "libseccomp-dev-dummy" for these.
> In the latter case package maintainers would have to
Russ Allbery wrote...
> Christoph Biedl writes:
>
> > tl;dr: The file program in unstable is now built with seccomp support
> > enabled, expect breakage in some rather uncommon use cases.
>
> Thank you very much for doing this! Here's hoping this sets a trend. It
> will provide so much defense
5 matches
Mail list logo
