Use flag "+lock" forces installation of xscreensaver when not explicitly unsat and not using one of the offered 3 screensavers (xscreensaver, gnome-screensaver, xlockmore - I'm using slock on an old laptop). Probably it'd be better to have some kind of virtual for that. Reproducible: Always Steps to Reproduce: 1. ensure not to have "lock" or "-lock" in xfce-utils' use flags 2. emerge slock 3. emerge -uNva xfce-utils Actual Results: xscreensaver is forced to install Expected Results: portage should recognize already installed screensaver
# ChangeLog for xfce-base/xfce-utils # Copyright 2000-2008 Gentoo Foundation; Distributed under the GPL v2 # $Header: /var/cvsroot/gentoo-x86/xfce-base/xfce-utils/ChangeLog,v 1.124 2008/09/24 15:43:07 angelos Exp $ 24 Sep 2008; Christoph Mende <angelos@gentoo.org> metadata.xml, xfce-utils-4.4.2-r1.ebuild: Added lock USE flag for screen locking, bug 235092 This isn't about portage or ebuilds - it all depends on whether xfce-utils can use slock or any of the other screen locking alternatives apart from xscreensaver/xlockmore/gnome-screensaver.
well, it cannot. xflock4 only checks for xscreensaver-command, gnome-screensaver-command --lock and xlock, so even if I'd include slock in RDEPEND it won't be able to use it. I've filed an upstream bug to include xtrlock, alock and slock.
other locking apps will be added to the ebuild as soon as upstream adds them to xflock4
