Slashdot Mirror
Fedora 13 Is Out
ultranerdz writes "Fedora 13 has just been released. It includes major features such as automatic print driver installation, automatic language pack installation, redesigned user account tool, color management to calibrate monitors and scanners, experimental 3-D support for NVIDIA video cards, and more."
Parent is talking about the Presto Plugin for yum. http://fedoraproject.org/wiki/Releases/FeaturePresto
Hey... he's a well paid sysadmin, give him a break. ;)
Remember to maintain your supply of
You are joking I hope.
Having used both rpm and apt for a long time now in a sysadmin setting, I can say that both have their pluses and minuses. rpm to me has a much more professional feel to it IMHO. I really wish that dpkg had the -V flag like rpm does, I've used that more times than you probably could imagine. rpm always seems faster at finding a package name given a file path and at listing out the files in a package. On the flip side, rpm historically hasn't had good depenencies and I never liked how they always wanted to compile in support for everything in rpm, which is one reason I liked being able to configure all that in emerge on Gentoo. Plus rpm used to have all kinds of problems with the database getting locked or corrupt. I switched to Gentoo as a workstation a while back when I tried to uninstall kernel-source and it said I couldn't because some audio library depended on it. That just shouldn't ever happen. But then I switched to Ubuntu because Gentoo development goes so fast that if you don't emerge -pv system practically every night, you end up not being able to upgrade at all.
So the point is that there are always reasons for the various package management systems being the way they are and because most people are unique, there are always going to be people who like those different features. You shouldn't poke fun of their choices until you understand them better. Hence the phrase, don't judge a man until you've walked a mile in his shoes.
Speaking of issues with apt-get, my old comment:
When doing large scale automated apt-get update; apt-get upgrade tasks, ask what happens to apt-get/dpkg when a postinstall script fails, or there were file conflicts with another package. Yes, the machine never fetches updates again. Serious amounts of dpkg --configure -a, dpkg --purge --force-reinstreq, and apt-get -f install are required to even get it working again. Also don't ask what happens when a user wants to install a local package with dpkg -i that has a missing dependency. Yes it prints an error, but unknowingly to the user the package actually gets half installed and breaks the automated update jobs. Why isn't there a --force flag to prevent this from happening?
Yum and rpm have had these issues solved for years and years, why can't Debian fix it?