Future problamatic updates solution(?)
Maybe what we should do for future items (similar to glibc2.1) in order to
minimize the global devel affect (mainly to keep those people who complained
about the glibc2.1 upgrade happy) is to do the same thing that is being done
for the gnome stuff. For example, we all know that the future perl upgrade
is going to break stuff...so what we do is have the maintainer of perl throw
his/her new packages up on his site on master (or wherever) and set it up for
apt-get access...(plus allowing for maintainers of perl based packages to place
their files there as well) so that those who want to test the new stuff out
(like me) can do so and those who wish to wait till they are semi-stable can.
This would also allow for perl-based package maintainers the opportunity to
fix their packages before the new perl is dumped into the devel tree.
I am willing to put my machine up as a development box for perl stuff (or for
any debian devel stuff in general). Those who want to work on packages for
glibc2.1 or the future perl (or anything for that fact) but don't want to
mess with their own machines (maybe you only have one and you want it to work)
you can have an account on my machine to do testing/building/whatever.
Ivan E. Moore II Rev. Krusty
GPG Fingerprint=3291 F65F 01C9 A4EC DD46 C6AB FBBC D7FF 0E1A 75E3