| |||||||||||||
Ladislav Bodnar's reportingLadislav Bodnar's reportingPosted Jun 11, 2004 14:19 UTC (Fri) by ekj (guest, #1524)In reply to: Ladislav Bodnar's reporting by ballombe Parent article: Gentoo Package Management with Portage Actually, the entire thing is years out of date.<p> These days, every serious linux-distro provides package-management that deals with dependencies.<p> It is true that people *used*to* complain about this years ago, but these days the only reason you'll see more incompatibilities and messed dependencies for *rpm than for *deb is that there's a lot of different distros using rpm, and basically only debian using deb.<p> Thus you risk getting stupidity when trying for example to install a redhat-rpm on mandrake. Perhaps redhat uses foo-1.2.70 and the redhat-package you want to install depends on it, while mandrake has upgraded to foo-1.4.3, and kept on the older one as foo12.70 for compatibility-reasons.<p> End result; the package will claim that you ain't got foo >= 1.2.70, even though you do. This ain't an rpm-problem but a problem caused by different distros giving different names to the same stuff.<p> "urpmi gimp" does exactly the same thing as "apt-get install gimp" and urpmi --auto-select does the same as whatever command the debianers use to update all packages to the latest version.
(Log in to post comments)
Ladislav Bodnar's reporting Posted Jun 11, 2004 18:30 UTC (Fri) by piman (subscriber, #8957) [Link] > these days the only reason you'll see more incompatibilities and messed dependencies for *rpm than for *deb is that there's a lot of different distros using rpm, and basically only debian using deb.There's a lot of distributions using .deb, actually; the difference is that Debian has an extensive packaging policy, which anyone can read and use. So all the third party distributions have packages that more or less follow that policy. The other distributors also usually work with Debian to the extent that their goals allow. Policy is the real strength of Debian's packaging system, and the reason that you don't find many incompatible third party .debs. > "urpmi gimp" does exactly the same thing as "apt-get install gimp" and urpmi --auto-select does the same as whatever command the debianers use to update all packages to the latest version. Last time I checked, RPM (and URPMI) had no equivalents of APT pinning (manage specific sets of packages from other sources), large-scale downgrading, deborphan and debfoster (automatically remove unneeded packages), auto-apt (automatically install packages when something on the system requests a file from a package), debhelper, (a consistent way to create packages), and a dozen other tools that make up the Debian packaging system. It's true that most other distributions have caught up to the level of sophistication that Debian's packaging tools were at -- 4 years ago. Installing and upgrading packages is the *bare minimum* a package manager should be able to do.
Deb vs. RPM Posted Jun 14, 2004 16:41 UTC (Mon) by EricBackus (guest, #2816) [Link] And yet, deb (or rather, apt) still doesn't automatically handlecryptographically signed packages, right? So you can auto-update, downgrade, whatever, but you don't *really* know what you have when you're done.
|
|||||||||||||