[ale] Lost in updateville

[Michael Hirsch]

On 4/15/05, Sean Kilpatrick <drifter at oppositelock.org> wrote:
> Being a firm believer in the notion that what you do NOT know
> can sur'in hell bite you in the butt, I have a question:
> 
> First a preface:
> 
> Was told last night at the ALE meeting that the only way to solve
> my CD burning issues was to do a clean update of KDE rpms using
> the material available on SourceForge. So, this morning went off to
> SourceForge and am ready to follow directions -- only I don't
> trust them.

I didn't say "the only way" I said "one way".  And I have no idea if
this will solve your burning issue, I said it would upgrade your K3B
installation.
 
> I am told to download a file [kde-redhat.repo] and drop it
> into /etc/yum.repos.d/   (I am using yum 2.1.11 on a FC3 system.)
> Did that.
> 
> This is a text file with pointers (?) to kde-redhat-stable,
> -stable-all, -kde-redhat-testing, -testing-all, -unstable, and
> -unstable-all.  I do not think I want to be downloading material
> from the testing and unstable repositories. Yet my yum.conf file
> has a line "pkgpolicy=newest".
> 
> So much for the preface. My question is this:
> 
>   Do I need to edit this file [kde-redhat.repo] to remove references
> to the testing and unstable branches? Or comment them out with "#" ?

Looks to me like you should comment out all the testing and unstable
stanzas, leaving in the  stable stuff.  I'd say the instructions are
weak.

There appears to be better documentation for using the apt repository
than yum.  I've always used apt, myself, with good results.  And apt
has synaptic for a nice GUI front end.

Michael