On 06/06/12 22:45, Mick wrote:
On Wednesday 06 Jun 2012 20:30:19 Nikos Chantziaras wrote:
On 06/06/12 21:30, Mick wrote:
Latest stable portage told me this:
* Messages for package app-portage/portage-utils-0.10:
* /etc/portage/postsync.d/q-reinitialize has been installed for
convenience * If you wish for it to be automatically run at the end of
every --sync: * # chmod +x /etc/portage/postsync.d/q-reinitialize
* Normally this should only take a few seconds to run but file systems
* such as ext3 can take a lot longer. To disable, simply do:
* # chmod -x /etc/portage/postsync.d/q-reinitialize
but it did not tell me *why* and I don't understand what "Reinitialize
ebuild cache" mean.
In case this makes any odds, I am using eix. Do I need the above script?
The q tool has it's own database. q-reinitialize updates it. It takes
0.1 seconds to complete, so you can just activate it and forget about
it. You can also execute it manually to see how fast it is.
Thanks Nikos, is this a database to be used by the q tools, or for some other
purpose?
It's used only by q.
I am trying to understand if I will be duplicating what eix does.
It's not the same as eix. It's a bit similar to equery, except it's
blindingly fast. Compare for example the speed of:
equery belong /bin/bash
vs:
qfile /bin/bash
q is orders of magnitude faster. I have both though, since some things
can be done with the one but not with the other.
