FS#17477 - [xfce-utils] xflock4 requires xlockmore
Attached to Project:
Arch Linux
Opened by Peter Avramucz (muczyjoe) - Saturday, 12 December 2009, 12:32 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 12 May 2010, 20:15 GMT
Opened by Peter Avramucz (muczyjoe) - Saturday, 12 December 2009, 12:32 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 12 May 2010, 20:15 GMT
|
Details
Description: xflock4 (extra/xfce-utils) requires xlock
(community/xlockmore).
Perhaps a postinstall message should be added to extra/xfce-utils. |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Wednesday, 12 May 2010, 20:15 GMT
Reason for closing: Fixed
Additional comments about closing: added optdepends to trunk for next build.
Wednesday, 12 May 2010, 20:15 GMT
Reason for closing: Fixed
Additional comments about closing: added optdepends to trunk for next build.
if test x"`which xscreensaver-command 2>/dev/null`" != x""; then
xscreensaver-command -lock
elif test x"`which gnome-screensaver-command 2>/dev/null`" != x""; then
gnome-screensaver-command --lock
else
xlock $*
fi
As you can see, any of the three main screensaver applications will work. As such, I believe common sense should prevail and the user should be able to figure out on his/her own that a generic screen locker frontend would require a screensaver/locker program with which to interface. At most, all three should be added as optdepends, but I think even that is excessive.