On Fri, Mar 07, 2003 at 02:59:37PM -0500, Joey Hess wrote: > Anthony Towns wrote: > > * What else needs to be done to get Perl, Python, Gnome 2, KDE 3, > > postgresql 7.3, and various other major subsystems out of > > unstable and into testing? ... > I hope that as many packages as possible can just be rebuilt with gcc > 3.0 just cause it's better, but since we have no way to track what has > built with what generally, who knows. > ahh, what? Would it be so hard to have the archive maintenance software grep new packages that get accepted, see what they were compiled with, and store that data somewhere? I'm sure there's some gcc 3.2 specific symbol that we can grep for in newly uploaded packages... It seems like this would be tremendously useful for gauging the progress of the transition, and for qa to be able to identify bugs that are caused by gcc3.2 compatibility issues. -- michael cardenas | lead software engineer, lindows.com hyperpoem.net | GNU/Linux software developer people.debian.org/~mbc | encrypted email preferred "Searching for the Truth through words and speech is like sticking your head in a bowl of glue." - Yuan Wu
Attachment:
pgpERaRo6xmhJ.pgp
Description: PGP signature