On Monday 28 November 2005 00:20, Ned Ludd wrote:
> On Mon, 2005-11-28 at 00:15 +0900, Jason Stubbs wrote:
> > On Monday 28 November 2005 00:01, Ned Ludd wrote:
> > > The following untested attached patch removes CDEPEND from ebuild.sh
> > > A quick grep -i shows that there is one case of CDEPEND left in
> > > pym/portage.py after applying the patch. It's in the auxdbkeys around
> > > line 5130. Not sure if that is safe to remove or not.
> > > The cache entry for CDEP has been replaced with a blank line to keep
> > > the cache format compatible.
> >
> > The CDEPEND in auxdbkeys is needed, but it won't cause any harm other
> > than the extra 10 or 11 bytes added to portage.py. This patch is pretty
> > much perfect as it is. :)
>
> Great.
> So it's all in your hands now then I can assume and I don't need to file
> a bug? ;-)

Committed.

> Anything else pending before .53 hits stable?

I don't believe so. I'll give it until Wednesday 12:00 UTC and put it out then 
if nothing comes up. I don't expect anything to, but I'm having a couple of 
whiskeys atm before bed and will be heading out to a drinking establishment 
tomorrow... ;)

> You know I can be somewhat impatient and I'm ready to get started on
> making patches for .54

As are we all. However, the wait seems to be doing good. While trunk is has 
been reopened for a while, the only things that have gone in have been in 
testing outside of trunk for a while which has improved quality greatly. 

Given people's expectations of what 2.0.54 should be I'm not sure of what will 
happen with 2.1/2.2. However, given the quality that trunk currently has it 
might be best to split off a branch and lock down the changes in 2.0.54 as 
soon as the first _pre is released. As far as I know, everything I listed in 
my last email to the ".53, .54.." thread have existing tested patches so we 
can probably get a 2.0.54 up to where 2.0.53 is now in half the time...

--
Jason Stubbs

-- 
[email protected] mailing list

Reply via email to