This is needed by new tracker versions =app-misc/tracker-1.8.1 =gnome-extra/nautilus-tracker-tags-1.8.1 If you cannot keyword it, it's possible to skip the requirement... but tracker upstream strongly discourages to do that Thanks
libseccomp is already keyworded for all the arches it possibly can be. if it's missing an arch, it's because the kernel is missing support on that arch. USE=seccomp is already masked for these arches specifically with a comment saying it hasn't been ported yet. if upstream is making libseccomp a *hard* requirement, then they just don't know what they're doing, or they don't care.
The probably don't care much about that arches :/ Well, in that case, we can skip the requirement for them I guess and rely on the old behavior before: https://git.gnome.org/browse/tracker/commit/?h=tracker-1.8&id=e1761a93d3d5483a511cb702717d7ef67577c54e The problem is that they consider that setup as non secure :/
you can say that about any program not using seccomp we already have USE=seccomp for exactly this, and it's turned on by default in the profile
there's really nothing that can be done here on Gentoo's side. libseccomp functionality depends entirely on people porting seccomp to their arch in the upstream kernel. short of doing all those ports ourselves, it's not going to change. the use of libseccomp itself should be controlled via normal USE flags. it's pretty unlikely that the code is written such that it can't work w/out seccomp.
I see two options: - Drop tracker keywords on those arches (I would opt for this option as I really wonder is that arches are still having any user of tracker) - Skip the dependency on that arches even showing that security warning (that wouldn't be a regression... tracker would behave as it was doing in older versions)
[master c021dbe] app-misc/tracker: Version bump, handle optional (and recommended, default on) seccomp support via USE flag as suggested by vapier in bug #602138. 2 files changed, 262 insertions(+) create mode 100644 app-misc/tracker/tracker-1.8.3.ebuild
