View Single Post
SubCore's Avatar
Posts: 850 | Thanked: 626 times | Joined on Sep 2009 @ Vienna, Austria
#90
Originally Posted by rm42 View Post
Can you elaborate? I would be interested in seeing the points he makes rebutted.

the few things i noticed:

1. Upgrading packages
There's no notion of "upgrade" action in dpkg/apt.
apt-get upgrade maybe??
(at that point i already knew he doesn't really have much experience with debian packaging...)


2. Dependency tracking
One can successfully "dpkg -i" a package with an unmet dependency. Such package
will be installed but not "configured" rendering it unusable. RPM won't allow
such action, as it will fail saying there are unmet dependencies.
dpkg -i won't install stuff without dependencies. you have to --force-things or --ignore-depends for that to happen.
dpkg -i without either of those additional parameters will fail when encountering unmet dependencies.


3. The scripts problem.
Sometimes a package with broken pre-uninstall script is installed.
dpkg --force-remove-reinstreq


4. Build process documentation [...]
On the other hand, all the deb package creation documentation heavily orbits
around the debian policies about freedom, distributions, maintainers, and other
uninteresting BS.
mhm...
centralized debian documentation > fragmented rpm documentation IMO


5. The build files [...]
now that part's a rant from someone in unfamiliar territory, nothing more.


7. Speed
that's a maemo-specific problem. actually, it's an application-manager specific problem. has nothing to do with apt/dpkg helpers. (apt-get install something in xterm will NOT trigger a DB rebuild, it IS cached).


8. The /opt problem
i doubt that just using .rpm and prefices/macros will magically solve this problem. many things won't "just work". that's hopelessly optimistic
__________________
"What we perceive is not nature itself, but nature exposed to our method of questioning."
-- Werner Karl Heisenberg
 

The Following User Says Thank You to SubCore For This Useful Post: