[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: gcc 3.2 is now the default compiler in unstable

Matt Zimmerman wrote:
I can say that I expect this to take atleast 6 months, probably more.

Unless there is divine intervention, you won't even see parts of it before that.

Why do you say this?

Because I can :-) Seriously, the current update_excuses mechanism is very conservative about migrating things. For example, as long as glibc has release-critical bugs, *no* package at all will migrate to testing, since they all depend on glibc. Even though changing the default Python has completed for many weeks now, migration isn't happening, since a single release-critical bug in any Python package, or any package that a recently-rebuild Python package depends on can stop migration of all other packages.

I haven't checked, but I would expect that migration of gcc-defaults itself would render a number of packages in testing uninstallable, because they happen to depend on earlier gcc versions (on purpose or by mistake). Then, the updating mechanism won't migrate gcc-defaults into testing. So I expect that magic is needed to override the conservative updating procedure.

As for needing 6 months for the migration even in unstable: Many release-critical bugs will be filed against various packages, as they fail to compile or work with g++ 3.2. Fixing those problems will take real manpower, delaying the transition by many weeks, per stratum (from libstdc++).


Reply to: