Luca Dionisi wrote: > If I got it, you mean that any pkg installation that > wants to add things to that database will use this program. Right? Yes. It works in a similar way to gconf - package provides raw files, runs that app to register them in the database. Ofcourse, the workaround for gconf is nowhere near as neat (since to register gconf schemas, the install scripts use gconftool-2, which is also useful to non-package users).
> Just a thing: this way, also a common user could add things to the > scrollkeeper db. Is this ok? In general, I can't see it being a problem - the only real danger is from malicious scripts updating Scrollkeeper, which isn't realy a worry (there's no real damage to be done there). > And installing again shared-mime-info didn't solve also the Nautilus issue? > Or had you already trashed it? I had already trashed it. > I think that I'm going to try and re-install the packages of gnome-core > paying more attention to permissions on files of these pkgs: > shared-mime-info > Gnome core packages (as in BLFS book) > Perhaps I'll create a new group for these files. You shouldn't need to. I tried this my first time around, and I actually ended up having a few more problems than what I've had this time (mostly because I ended up with an unmanagable mess). Unless there's some specific reason to prevent other packages installing stuff into GNOME, making a few install dirs should be enough. -- Lennon Victor Cook -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page