https://bugzilla.novell.com/show_bug.cgi?id=761473
https://bugzilla.novell.com/show_bug.cgi?id=761473#c5
--- Comment #5 from Nelson Marques
The x11.so renderer is there, however it is packaged inside the plymouth-devel package.
Ok, I digged up a bit and found out that you probably used Red Hat/Fedora as a reference (they do the same)... In my opinion we can improve here... keep on reading...
As you indicated already for normal usage the x11.so renderer is not used.
The x11 renderer allows you to run plymouth on a window in any environment which has a valid DISPLAY. This is not only meant to develop themes, but also to test them without having in fact to install, rebuild initrd and reboot... So there's even use cases available for normal users...
However if you started developing themes and want to test them, then you should install the plymouth-devel package which delivers you the tools :-)
First, I disagree with that statement. To write a __plugin__ you need the development package. To write a theme you don't need the development package if you are using one of the supplied plugins or no plugins at all... In my case I'm using the 'script' plugin so I don't need anything from the development package. Though for easier testing I want the x11 render to be present... Following your suggestion, this is what happens: - Installing the 'devel' package will polute my system with loads of dependencies (devel) which are totally unwanted on my system, specially because there's no reason for having them installed. My suggestion is that we can split the renderer into a separate package which is not devel. This would allow any user to test any plymouth theme without the need of having the initrd rebuild and rebooting the system. Furthermore, it would not drag into people's system a huge load of devel packages that will __NOT__ be used for the sole purpose of testing a theme... Having the renderer on another package would also not make it part of the default install as plymouth won't have an explicit dependency on it; this would allow us to keep only the __minimum__ files on the initrd... so it does grow bigger than it's actually necessary. I'm willing to do this changes and submit them to plymouth, if it's ok with you... basically just split the x11 renderer to another package, ex: plymouth-x11-renderer. Or if you prefer add it to the package which provides the logging tool for plymouth (which is documented since 2010 that will disappear in plymouth 0.8.4) Would this be ok with you ?
I don't know why zypper doesn't provide you with the same information, but rpm does:
HQVMT4XX20:~ # rpm -q --whatprovides /usr/lib64/plymouth/renderers/x11.so plymouth-devel-0.8.4-10.4.x86_64 HQVMT4XX20:~ #
The 'rpm' provides only the information on packages that are installed! So if you don't have that package installed, it's not visible to RPM (which was my case). Try 'rpm -e plymouth-devel' and then 'rpm -q --whatprovides' and see if returns any result ;) While 'rpm' picks up the information from the local rpmdb (somewhere in /var), zypper should use the repository metadata (which includes all packages available on repo, installed or not). That's why I used zypper in the first place... I don't know zypper mechanics but I do know YUM mechanics... In YUM it would've worked. But this is off-topic. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.