In my opinion, it does more sense to keep the prelink cache in /var/lib instead of /etc, where it currently is. sys-apps/preload also keeps its cache in /var/lib.
perhaps /var/cache would be even better. its a cache, afterall.... however, it may live in /etc/ to guarantee is exsistance during boot. /var may be on a network file system... reassigning to maintainer.
yes, that is exactly why it's in /etc and not /var ... same goes for /etc/ld.so.cache all the other files used to calculate that are stored in /var already you're certainly free to pass the --cache-file= to whatever file you want on your system and change the crontab script ... only piece missing is whether portage let's you pass custom options to its hooks
Ok, thanks for the info. But in that case, the preload cache should also go into /etc to keep things consistent, shouldn't it?
i dont know what you're talking about. prelink.cache already is in /etc/.
Nope, I meant the preLOAD cache (sys-apps/preload), which currently resided in /var/lib
thanks for clarifying ... preload isnt really the same though. its cache isnt used implicitly by the C library, it's used by a daemon. in order for the daemon to be up and running, things like /var need to be mounted. i'm just guessing though as we dont maintain that package
Hmm. Is there a way to allow the user to choose the location of the caches? Maybe a config file? While I agree that it makes sense to keep the cache in /etc, it is not the way the filesystem layout was meant to be. It may only be a minor issue, but kind of hurts the perfection :)
doesnt /etc/conf.d/prelink already support whatever options you want ?
In theory it should. But the cron script doesn't seem to pay attention to that file, and prelink has no init script or something like that. The point of that config file eludes me.
Ok, disregard my last comment. It actually works with the cron script. I just had to create the dir that contains the cache file. prelink won't do that itself.
Closing then.
*** Bug 375833 has been marked as a duplicate of this bug. ***
> doesnt /etc/conf.d/prelink already support whatever options you want ? No, conf.d/prelink does not suppor "moving" of prelink.cahe, see changes needed in my patch here: https://bugs.gentoo.org/show_bug.cgi?id=375833 Also, I think that prelink info is saved in the binaries and prelink.cache is only needed to recalculate info during prelink run. So there is no need for it during boot. So why it is in /etc?
I propose reopening of the bug.
