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