[Bug 196379] Review Request: kdeartwork-extras: Artwork Extras, including xscreensaver-based screensavers

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: kdeartwork-extras: Artwork Extras, including xscreensaver-based screensavers


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=196379





------- Additional Comments From mtasaka at ioa.s.u-tokyo.ac.jp  2006-10-01 09:15 EST -------
Umm..  I must explain why I wonder for xscreensaver-base dependency
as xscreensaver maintainer in FE.

(In reply to comment #17))
> Because many of the kde screensavers actually use xscreensaver
What do you mean by "many of the kde screensavers"? 

This means that many KDE screensaver "hacks" (not "daemon") uses xscreensaver
"daemon" (i.e. /usr/bin/xscreensaver) ? 

(In reply to comment #18)
> But do all the xscreensaver-based screensavers actually *work*?  
> I'd venture possibly not, because %configure checks for the hacks 
> location at buildtime, and
> in the absense of that, it may just end up guessing.

Yes, configure of this package tries to check for the path of xscreensaver
hacks, and NO hacks are included in xscreensaver-base. So mockbuild without
xscreensaver-base correctly finds correctly all xscreensaver hacks 
(as all hacks are installed in the two hacks).

xscreensaver-base includes only the files related to xscreensaver "daemon".
And all the hacks packaged in xscreensaver-{extras,gl-extras} can actually
work without xscreensaver-base because all hacks in xscreensaver does NOT use
xscreensaver daemon, they are completely stand-alone.
This is why xscreensaver-extras, xscreensaver-gl-extras does not require
xscreensaver-base (this is very intentional), and gnome-screensaver 
can use xscreensaver-related hacks without xscreensaver-base.



-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.