| 1 |
On Friday 29 April 2005 23:26, Elfyn McBratney wrote: |
| 2 |
> On Friday 29 Apr 2005 15:11, Jason Wever wrote: |
| 3 |
> > On Fri, 29 Apr 2005, Jason Stubbs wrote: |
| 4 |
> > > The initialization time of portage is directly related to the number of |
| 5 |
> > > packages installed. Cutting out excess ebuilds from the tree won't |
| 6 |
> > > speed this up at all. Cutting out excess ebuilds won't have much effect |
| 7 |
> > > on the general running of emerge at all, actually, except for updating |
| 8 |
> > > the cache after syncing. |
| 9 |
> > |
| 10 |
> > Does that include the about >=10 second delay when emerge is first run on |
| 11 |
> > a box after a reboot before you get any visible output on the screen, or |
| 12 |
> > is that an entirely different problem? |
| 13 |
> |
| 14 |
> Heh, I get that after every invocation of emerge. :) |
| 15 |
|
| 16 |
Yep. That's the scanning of all installed packages for any provided virtuals. |
| 17 |
|
| 18 |
Regards, |
| 19 |
Jason Stubbs |
Archives