| 1 |
On Tue, 2009-10-13 at 12:37 +0200, Fabian Groffen wrote: |
| 2 |
> On 13-10-2009 11:09:11 +0100, Alan Hourihane wrote: |
| 3 |
> > > Yes it happens everytime, regardless of sync. |
| 4 |
> > > |
| 5 |
> > > For example, if I do say.... |
| 6 |
> > > |
| 7 |
> > > emerge net-ftp/lftp |
| 8 |
> > > |
| 9 |
> > > It does a bunch of updates before it starts "Calculating dependencies". |
| 10 |
> > > |
| 11 |
> > > And for |
| 12 |
> > > |
| 13 |
> > > emerge --sync |
| 14 |
> > > |
| 15 |
> > > It does a bunch of updates before the sync happens, then a bunch of them |
| 16 |
> > > again after it's finished. |
| 17 |
> > > |
| 18 |
> > > Alan. |
| 19 |
> > > |
| 20 |
> > > |
| 21 |
> > |
| 22 |
> > Here's what happens with an emerge --sync.... |
| 23 |
> |
| 24 |
> could this be related to statvfs? Sounds like Portage can't see that |
| 25 |
> the files still have the same timestamp, and hence reparses them |
| 26 |
|
| 27 |
Don't think so, as the statvfs call is only made to check there's enough |
| 28 |
storage space. No date/time checking. |
| 29 |
|
| 30 |
Alan. |
Archives