On Tue, 2004-12-14 at 00:15 -0600, Derek P. Moore wrote:
With the standard FreshRPMs, NewRPMs, Dag RPMs, and Dries RPMs in your repository list, it's as simple as:
yum install libgc libgc-devel glibmm glibmm-devel gtkmm24 gtkmm24-devel \ libsigc++2 libsigc++2-devel
or shorter: yum install gtkmm24-devel libgc-devel
The rest are pulled in by dependency resolution. (argh, annoying that there are packages with different names providing GC...)
Especially if you're in the world of Fedora Core 3, you should ditch fedora.us and livna.org in favor of FreshRPMs/NewRPMs/Dag/Dries combo.
Currently Red Hat has really screwed up the Fedora.us->official Extras transition, I agree with that much. However, the Fedora.us packages have the nice property that they actually see some QA before getting published. Personally I see that as a good thing. The wrong typo/thinko in a spec file really can do some pretty serious damage to your system, and with the one-person repos I don't know who checks the packages at all. To me it sounds like a good idea that someone other than the packager gives the package a once-over before spreading it worldwide...
By the way, livna.org has an FC3 rebuild. It depends on the FC2 Fedora.us packages though. Basically, apart from some C++ libraries this mostly works.
I've sent a self introduction to the Fedora.us development list, so hopefully I'll be able to get the packages in QA soon.
You're wasting your time. *smile*
Heh. Long term, the Red Hat hosted Extras should definitely be the canonical add-on for Fedora Core, and the stuff going in there to begin with is what's in Fedora.us now. Going with th others at the moment may work just fine, but might put you in a hole later; likely one that you can dig yourself out of if you know what you're doing, I admit. I at least wanted the option to stick with the Fedora packages.
/Per