Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-portage-dev
Navigation:
Lists: gentoo-portage-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-portage-dev@g.o
From: Ned Ludd <solar@g.o>
Subject: Re: .53, .54 and beyond...
Date: Fri, 25 Nov 2005 10:31:59 -0500
On Sat, 2005-11-26 at 00:01 +0900, Jason Stubbs wrote:
> Hi all,
> 
> I don't think there's really anything else that can be done for 2.0.53 so am 
> thinking that we should probably push _rc7 + docs out and let the arch teams 
> mark it stable when they're ready (or stick with 2.0.51.22-r3 if it pleaseth 
> them).

[snip]

> There's a few things listed on the new 
> (still unreleased?) project index and I'm looking to get the dependency stuff 
> refactored and moved out of emerge.. What are the shortterm goals?

For me my short term goals are to see these things happen

* post_sync action hook (.53/.54 )
* pax-utils depends ( .53 )
* new prepstrip offering splitdebug ( .53/.54 )
* misc cleanups of dyn_install (.54 )
* seeing CDPEND stop being created for the VDB ( .53 )
* flattened vdb {P,R,}DEPEND (.54 )
* introduction of RRDEPEND to the VDB ( .54 )
* VDB prevention of single byte NULL entries being created. ( .54 )


-- 
Ned Ludd <solar@g.o>
Gentoo Linux

-- 
gentoo-portage-dev@g.o mailing list


Replies:
Re: .53, .54 and beyond...
-- Marius Mauch
Re: .53, .54 and beyond...
-- Jason Stubbs
References:
.53, .54 and beyond...
-- Jason Stubbs
Navigation:
Lists: gentoo-portage-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
.53, .54 and beyond...
Next by thread:
Re: .53, .54 and beyond...
Previous by date:
.53, .54 and beyond...
Next by date:
Re: .53, .54 and beyond...


Updated Jun 17, 2009

Summary: Archive of the gentoo-portage-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.