1 |
On Wednesday 06 Jun 2012 20:54:58 Nikos Chantziaras wrote: |
2 |
> On 06/06/12 22:45, Mick wrote: |
3 |
> > On Wednesday 06 Jun 2012 20:30:19 Nikos Chantziaras wrote: |
4 |
> >> On 06/06/12 21:30, Mick wrote: |
5 |
> >>> Latest stable portage told me this: |
6 |
> >>> * Messages for package app-portage/portage-utils-0.10: |
7 |
> >>> |
8 |
> >>> * /etc/portage/postsync.d/q-reinitialize has been installed for |
9 |
> >>> convenience * If you wish for it to be automatically run at the end |
10 |
> >>> of every --sync: * # chmod +x |
11 |
> >>> /etc/portage/postsync.d/q-reinitialize * Normally this should only |
12 |
> >>> take a few seconds to run but file systems * such as ext3 can take |
13 |
> >>> a lot longer. To disable, simply do: * # chmod -x |
14 |
> >>> /etc/portage/postsync.d/q-reinitialize |
15 |
> >>> |
16 |
> >>> but it did not tell me *why* and I don't understand what "Reinitialize |
17 |
> >>> ebuild cache" mean. |
18 |
> >>> |
19 |
> >>> In case this makes any odds, I am using eix. Do I need the above |
20 |
> >>> script? |
21 |
> >> |
22 |
> >> The q tool has it's own database. q-reinitialize updates it. It takes |
23 |
> >> 0.1 seconds to complete, so you can just activate it and forget about |
24 |
> >> it. You can also execute it manually to see how fast it is. |
25 |
> > |
26 |
> > Thanks Nikos, is this a database to be used by the q tools, or for some |
27 |
> > other purpose? |
28 |
> |
29 |
> It's used only by q. |
30 |
> |
31 |
> > I am trying to understand if I will be duplicating what eix does. |
32 |
> |
33 |
> It's not the same as eix. It's a bit similar to equery, except it's |
34 |
> blindingly fast. Compare for example the speed of: |
35 |
> |
36 |
> equery belong /bin/bash |
37 |
> |
38 |
> vs: |
39 |
> |
40 |
> qfile /bin/bash |
41 |
> |
42 |
> q is orders of magnitude faster. I have both though, since some things |
43 |
> can be done with the one but not with the other. |
44 |
|
45 |
Got it. Thank you! :) |
46 |
-- |
47 |
Regards, |
48 |
Mick |