Submitted by Anonymous (not verified) on Mon, 2008/06/23 - 10:54.
...how something functionally simillar is going to provide any advantage. In my opinion:
1. RPM==DEB==back-end package manager.
2. YUM==APT-GET==front-end to package manager that provides dependency management using meta-data features of the back-end.
3. Package-Kit==Synaptic==GUI for the front-end which makes it simple to use features through a GUI.
Now, if you find a feature missing in Package-Kit or Yum that is present in apt-get, it should be trivially easy to log a feature-request through appropriate bugzilla systems and get it included.
To me, on Fedora/Red-Hat systems, yum has always been better integrated with the RPM-backend and therefore the choice is moot. The choice, if I were to use Debian, would of course also be moot - it would be apt-get.
I don't see...
...how something functionally simillar is going to provide any advantage. In my opinion:
1. RPM==DEB==back-end package manager.
2. YUM==APT-GET==front-end to package manager that provides dependency management using meta-data features of the back-end.
3. Package-Kit==Synaptic==GUI for the front-end which makes it simple to use features through a GUI.
Now, if you find a feature missing in Package-Kit or Yum that is present in apt-get, it should be trivially easy to log a feature-request through appropriate bugzilla systems and get it included.
To me, on Fedora/Red-Hat systems, yum has always been better integrated with the RPM-backend and therefore the choice is moot. The choice, if I were to use Debian, would of course also be moot - it would be apt-get.
YMMV.