Re: [gentoo-portage-dev] The road ahead...

[Brian Harring <ferringb@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 1672 bytes --]

On Sat, Oct 22, 2005 at 09:25:49PM +0900, Jason Stubbs wrote:
> On Saturday 22 October 2005 12:30, Brian Harring wrote:
> > On Sat, Oct 22, 2005 at 12:13:42PM +0900, Jason Stubbs wrote:
> > > Something like:
> > > * Add base class(es) for new cache framework
> > > * Add cache backend for XYZ database
> > > * Switch portdbapi to the new framework
> > > * Remove old framework
> >
> > eclass_cache.py chunking (portage.py removal)
> > cache replacement (base + implementations)
> > portage.py (dbapi), emerge changes (integration of new cache).
> > removal patch
> >
> > That said... would be curious about suggestions on how to do this
> > sanely.  Chunking the beast up (patch jockeying) after the fact I can
> > do, but in instances like this... it's not easy to chunk it down into
> > features/tweaks.  Basically is big ass blobs of "new stuff",
> > "conversion to new stuff", "remove old stuff".
> >
> > Even with that... still is tricky.
> >
> > Offhand, the existing cache patch could be reduced pretty heavily by
> > breaking it down into addition, and removal of old cache.
> 
> Heh.. You're rambling a bit here. Addition, conversion, removal is pretty much 
> what my list is above. The only difference being that the individual backends 
> are separated out as well.
At least I'm not arguing with myself... ;)

> The most important thing in the case of this patch-set is that it can be 
> easily seen how the new framework works and how existing code changes to 
> accomodate it. The removal of the old stuff and the reworked backends are 
> really auxillary.
Yah.  Will chunk up the patch today/tonight and repost.
~harring

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]