Emerald no borders - funny portage behavior

[alamuru420123]

I've had compiz-fusion working for some time and then did a complete update after which it stopped working. So, today I decided to take a look and compiz started working but emerald didn't.

After looking around on google for a while and not finding anything, I decided to see if a re-emerge would help. But when I tried an emerge emerald -pv, it gave me an upgrade message from 0.5.4 to 0.7.8.

The funny thing is, I tried an emerge -uDNpv world and it didn't show emerald.

I did an emerge emerald and now everything is working fine.

Just wondering if this is some peculiar behavior specific to emerald. I checked all the /etc/portage files and though emerald is unmasked it is not tied down to a particular version.

Any thoughts?

[krinn]

could be if (saying cf instead of compiz-fusion, yeah i'm so lazzy)

- cf 1.0 need emerald 1.0
- emerge cf -> emerald 1.0 is installed too as dependency -> cf add to world
- emerge -uDN world will so take emerald and cf (as emerald depend on cf)

now after sync
- cf 2.0 no more depend on emerald 1.0 (or any version)
emerge -uDN world
cf is still in world, but emerald is not in world, and cf 2.0 don't need emerald as dependency and no other programs need it too = upgrade cf, but not emerald

you may now ask, is it the case? why emerald isn't anymore a dependency of cf while my cf wasn't working without it...
it simply could be the case, i use cf with gtk decorator

i suppose your old cf was using emerald decorator, must be why it rework when you install the new emerald version, but it could had work without emerald if you tried gtk-decorator instead.