[ATrpms-users] libmyth for fglrx

[Kevin J. Cummings]

Axel Thimm wrote:
> But rants aside try using smart as follows:
> 
> smart update
> smart fix

-bash: smart: command not found

so I guess I don't have smart installed and configured on this lappie.
I'm "supposed" to be using a vendor supplied update script, but I
slogged through it and started using yum repos whereever possible.
I probably have more repos configured than I need to (3 of them contain
a subset which entirely overlap).

The last time I tried to install configure smart on my FC5 system, I
gave up due to not understanding the repo-lingo sufficiently to make
intelligent decisions in setting up 3rd party repos that worked right.

My history is that I used to install RPMs by hand during my RHL days.
In my first Fedora installation (FC2), I installed and learned how to
use synaptic.  It was very useful to help me clean up my very old legacy
packages (some I wished to keep, some I needed to punt).  I migrated to
yum soon thereafter when yum became the default (was that FC3?)  I tried
 smart, but decided to let it wait when I couldn't make it do everything
I wanted it to for me.  (ie I couldn't configure it correctly.)

> And see how smart will (mostly) suggest the right steps to perform.

I wish smart would "auto-configure" itself for each repo!  *that* would
be useful!

>>> A runtime check would be best, of course, but that's a request to make
>>> to the mythtv developers.
>> I figured as much.  I think that the Myth Devs would probably prefer it
>> if the video drivers got it right in the first place!  Which is why I
>> was asking here.
> 
> You mean here is where ATI developers lurk around and will pick up
> this suggestion? :)

"not exactly."  I figured I'd run it past you and see what you were
willing to do before filing an RFE and discovering it was a waste of
time.   B^)

>> I was assuming that just providing a 2nd package (say libmyth-fglrx) and
>> have the user rpm --erase libmyth (maybe with --nodeps) and install the
>> replacement by hand.  Perhaps even uninstall the mythtv-suite meta
>> package to prevent the old libmyth from being brought back in by
>> updates.  Maybe I haven't thought things through far enough.
> 
> libmyth updates are not brought in by mythtv-suite, they are brought
> in automatically. And an upgrade to the next mythtv rpm release would
> require both packages to exist somehow in the repo, with both
> providing the same (packging) interface, but still no coinstallable
> and not cross-upgradable. It's a corner case that rpm/yum/etc cannot
> solve.

grumble.

> Oh, and libmyth and mythtv-suite are history anyway. See the versions
> in testing and bleeding. :)
> (not that it matters in this context)

Another bridge to cross when I get to it I suppose!

>>> I checked mythtv's tickets and no one ever requested to make the static
>>> USE_* flagg to a runtime flag. Actually in the tickets it is only
>>> mentioned once only, and in a different context, so most probably the
>>> flag hasn't become runtime yet due to lack of demand?
>> Do you have the MythTV ticket number for the one which resulted in this
>> flag being added?  I suppose I can go and try and search for it myself.
> 
> No, I don't, but it wasn't really relevant, just a developer asking a
> user to test it for another driver.

And lest I be remiss in my courtesy, thanks for all the hard work you do
providing all the addon packages to help make my Fedora experience better!

-- 
Kevin J. Cummings
kjchome at rcn.com
cummings at kjchome.homeip.net
cummings at kjc386.framingham.ma.us
Registered Linux User #1232 (http://counter.li.org)