On Tue, 2021-06-29 at 23:27 -0400, Bruce Ashfield wrote: > On Fri, Jun 25, 2021 at 11:21 AM Bruce Ashfield via > lists.yoctoproject.org > > > That is the core of what I was asking. A package that is now in core, > > > why is it only enabled by a distro feature ? > > > > > > > And for clarity, I realize that the systemd recipe checks for the > > systemd distro feature .. so that is similar. But systemd is one of > > many init managers, so I can see why it is used. > > I still don't have a better solution to this, and while I see about > getting seccomp behaviour changed in core, I can get this into the > tree. > > I've added the extra seccomp dependent recipes and expect to merge > this on Wednesday.
The reason for the distro_feature is to have a way to configure multiple packageconfigs on/off centrally. Some platforms don't support seccomp at all (riscv/arc) so forcing it on everywhere isn't possible. I think we can remove the DISTRO_FEATURE restriction in the seccomp recipe itself in core and replace it with a COMPATIBLE_HOST declaration. We could also add the option to the default distro backfill. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#6594): https://lists.yoctoproject.org/g/meta-virtualization/message/6594 Mute This Topic: https://lists.yoctoproject.org/mt/83767805/21656 Group Owner: meta-virtualization+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
