Just a quick look at their planned features compared to what's in dpkg
Not supported by dpkg, I think. In the dpkg world, this would probably be
handled instead by the providers of the virtual package manually
triggering via dpkg-trigger(1).
Supported by dpkg for a bit more than 1 year now. And it rocks.
Funnily though, their motivation is getting rid of ldconfig calls -- and
we were unable to get rid of them in debian using dpkg's file triggers.
RPM's file trigger syntax will need to be more expressive than dpkg's for
this to work. (We stopped worrying about this when ldconfig got a second
level cache that made it very fast to run.)
Supported by dpkg for 15 years or so, and Recommends are used by apt-get
and aptitude for a couple of years. (But dpkg does not have a Supplements
-- I don't know how that differs from enhances.)
Dpkg does not have separate scripts for upgrade, but I think its
arguments passed to the regular postinst and prerm are slightly saner
Not enough detail to say for sure whether dpkg's arguments allow doing
everything this will do. Their example *can* be handled by the arguments
dpkg passes to a postinst. But it sounds like a lot more info may be
(Looks like this won't be added to rpm yet.)
New payload format
Wow, switching from cpio to something else will break a lot of cheezy
rpm2cpio type scripts. Curious that they do not consider tar an option.
Maybe because tar has differing semantics than rpm with respect to
whether parent directories have to be included?
Tilde in version
Added to dpkg several years ago. Not clear if their chosen meaning for
tilde is compatible with dpkg's. (But IIRC, dpkg and rpm version
comparison is already not fully compatible.)
Easy way to add or remove autogenerated dependencies
Debs are built so much differently that there is really no way to