View Single Post
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#93
Originally Posted by fatalsaint View Post
This is actually a matter of preference. Having dpkg behave in this way allows me to then do "apt-get -f install" to automatically download and grab the dependencies for that package, and then properly install all of them. No dependency hell (meaning tracking them down myself, or yum installing them one by one), so to speak. What is the equivalent of this in rpm?
You'd have to install the dependencies first, then install the RPM. As you say, doesn't really make much difference.

Originally Posted by fatalsaint View Post
Somebody else will need to address 6.. I don't understand how RPM can magically allow a user to suid root a binary that debian can't. This looks like something that should be taken care of in a postinst type script and can only be done as root... and the .deb takes and packages up the files with the permissions that they were given when you build the deb package - so if you suid the binary as root, build the deb, and then install it - it will come out suid. I don't understand what he's getting at.
With RPM you can specify the specific ownership and file permissions that should be applied to the installed files - the permissions on the files pre-packaging can be completely overridden. As you say, can be done in postinst but RPM presents a slightly (IMO) cleaner way of keeping this data in one place.

I'd agree with you otherwise - I've used a variety of package types (mostly RPM at work, using apt4rpm, smart, and now yum; ebuilds at home, and debs on the N800 and N900), and there's little practical difference between them nowadays.

P.S. And please don't mention the abortion that is up2date anywhere around me...