Hi, I just emerged many of the gDesklets available because I like eye candy However, although it gave me no errors when I initally emerged them, now, whenever I do emerge -UupDv world, I get: [blocks B ] x11-plugins/desklet-diskinfo (from pkg x11-plugins/desklet-psisensors-20031028) [blocks B ] x11-plugins/desklet-networkinfo (from pkg x11-plugins/desklet-psisensors-20031028) [blocks B ] x11-plugins/desklet-cpuinfo (from pkg x11-plugins/desklet-psisensors-20031028) [blocks B ] x11-plugins/desklet-meminfo (from pkg x11-plugins/desklet-psisensors-20031028) They *appear* to coexist peacefully, and a quick glance at the output from qpkg doesn't show any conflicts between the packages. Another thing that's odd is that it let me emerge them all without showing any blocks at first, and then afterwards when I did emerge --update --deep --pretend world, the blocks started to show up, leading me to wonder if this is a problem with portage or these ebuilds themselves. Thanks!
Hi there, I'm not sure with regards to the blocks not showing up, it's unlikely to be a portage problem, perhaps I can look at that some more. What I am sure about however, is they do in fact block each other, they both install the same sensors (see Sensors/CPU for example). I really want to move away from the desklet-{disk,network,cpu,memo}info as they arent being maintained individually by the author anymore. Instead, they are released together as a set of displays (psidisplays) and a set of sensors (psisensors). Have a look at qpkg -f /usr/share/gdesklets/Sensors/CPU/__init__.py, which should show the conflict. I'll look into the non-blocking blockingness of them :) with regards to your emerge -u world situation, but they do actually block each other for a reason. Thanks, Mike.
closing.
