On Wed, 10 Feb 2010 10:20:09 -0800, Mark Knecht wrote: > So am I at any great risk doing an emerge -C qt-3.3 and then expecting > revdep-rebuild to fix up mythtv-0.21 with qt-4 using whatever it has > ffor qt3-support? > > I'm __really__ not ready to upgrade my whole MythTV setup 0.22 if 0.21 > requires qt-3 and the qt3 support stuff in qt4 doesn't work. That > would be very painful for me even given 6 weeks.
QT3 and QT4 are different, MythTV 0.21 needs QT3, 0.22 needs QT4. One good thing about this is that QT4 uses split ebuilds, so you need install much less of Qt for a Myth backend. Upgrading from 0.21 to 0.22 was painless AFAIR. I made a backup of the database but didn't need. You do need to upgrade all backends and frontends at the same time, but then it's just a matter of restarting them and you're OK. I did "emerge --onlydeps mythtv && emerge -B mythtv" first so that I could then run emerge -k mythtv on the server to minimise the time it was down. -- Neil Bothwick ... "I just forgot to increment the counter," Tom said, nonplussed.
signature.asc
Description: PGP signature
