Fedora Holds Summit To Map Its Future

lisah writes "Last month members of the Fedora community met for a three-day summit (wiki here) designed to chart a course for future version releases as well as to plan other Fedora projects. Team members say they want to leverage the enthusiasm of a community that has demonstrated a willingness to develop Fedora Extras (add-on features to the Core package) and support Fedora Legacy (past releases). Red Hat's community development manager, Greg DeKoenigsberg, said, 'Community contributors have proven conclusively over the past 18 months that they can build packages every bit as well as Red Hat engineers — better, in some cases.' In addition to creating several proposals that will be introduced the the community for input and feedback, the summit also gave rise to the newly-created position of Fedora Infrastructure Leader." Linux.com and Slashdot are both owned by OSTG.

Comments

Your error is not RPM's fault

[DragonHawk]

You almost always have to force the installation using --no-deps --force, because RPM binaries are usually targeted at a specific distro/version.

No. All binaries are targeted that way. When you run ./configure, it runs through a bunch of checks to figure out where things are and how they are configured, for all of the dependencies. And "dependencies" includes everything from special-purpose libraries to glibc and the kernel. It includes all the configure options, source defines, patches, compiler switches, and anything else that changes the configuration of the binary. RPM keeps track of all that stuff because that's the only way to be sure it will work. If you change any of it, sure, the resulting binary *might* *appear* to work, but it might just as easily segfault.

Binary compatibility is hard.

The "--force" switch tells RPM, "I know you think this is a bad idea. I say I know otherwise. Do it anyway". You can't then turn around and complain that things broke when you did that. RPM took your word for it when you said you knew better. If you didn't know better, that's your own damn fault, not RPM's.

Put more briefly: If you think you need to use --force, you're almost certainly wrong.