Okay… I posted a couple months ago about avast not installing on Fedora 11 x64. Now the RPM package won’t install on the x86 version, either. The only unmet dependency is “libexpat.so.0”
There is a symlinked libexpat.so.0 in /lib that I assume points to libexpat.so.1.5.2.
How do I make this work? 
hallo, when the liobrary is present, just force the installation using --nodeps. then, it should work. if not, tell us which library/symbol isn’t present there.
regards,
pc
Okay, thanks. Before I do this though, I’d like to know: Does Avast! Linux Home Edition provide on-access protection? I don’t want to have two AV daemons conflicting with each other and causing problems. I’ve never seen any Avast! daemon before when I’ve had it installed, but I’d rather hear it from Avast! than, say, Wikipedia.
The default installation not.
the daemons won’t conflict, but rather cooperate (when running under the same user-id, they share their SHM memory blocks, so they start faster etc.).
when they run under different UIDs, they will have nothing in common entirely.
regards,
pc
It seems to be working fine. I just did a test scan of my home directory.
Um. Does Avast! Linux Home follow symbolic links while scanning?
Hallo,
nope, they are scanned like normal files. It’s natural - the file exists once (so why to scan its linked aliases), and this way,we also minimise the peril of cycled links (loops).
But, links are resolved when given as starting point (you can start scan in a directory that is linked elsewhere). In general: links are followed, but aren’t recursed into.
regards,
pc
I’m aware this might count as thread necromancy, but I’m not sure a new topic is in order for this.
Using apt in one of its few working moments on Fedora 12, I’ve found the package needed to resolve avast Linux’s expat dependency: compat-expat. I don’t know if it’ll show up when someone tries to install avast now or not, but the package is there, and I want the Avast Linux forum to know.