| 1 |
On Fri, Aug 05, 2005 at 08:20:52PM +0900, Jason Stubbs wrote: |
| 2 |
> On Friday 05 August 2005 12:31, Brian D. Harring wrote: |
| 3 |
> > Hola all, patch (incvs now) to fix up a traceback on first sync with |
| 4 |
> > an empty tree; bug #96410 |
| 5 |
> > http://bugs.gentoo.org/show_bug.cgi?id=96410 |
| 6 |
> > |
| 7 |
> > The fix isn't exactly what I'd call pretty (creating an intermediate |
| 8 |
> > portdbapi and config instance to do the updates), but it's a corner |
| 9 |
> > case; config's categories is a bit of a hack, and tearing it out in |
| 10 |
> > stable is more work then worth... so this. |
| 11 |
> > |
| 12 |
> > Either way, it's attached, poke at it kindly :) |
| 13 |
> |
| 14 |
> You know the caching fairly well, so I'll ask rather than check. ;) |
| 15 |
> |
| 16 |
> How does this affect the new version of portage check that follows? Will |
| 17 |
> that use the old cache, find that it's out of date and then regen it? |
| 18 |
The ugly inlining of code in portage.py makes this play nice actually, |
| 19 |
due to the forced reload of portage prior to checking for an updated |
| 20 |
portage being available (specifically, the config instance is |
| 21 |
recreated). |
| 22 |
~harring |
Archives