Okay, I'll bite:
> RPM [...] Example: still uses mainly file-based dependencies
That's not true. It _can_ but primarily does not use file-based dependencies. I think, realistically, from a packaging perspective, you'll find places where both RPM and deb suck, and where they both have strengths — it's kind of half-a-dozen-of-one, six-of-the-other. From a user perspective, it barely ever matters even a little bit.
> Another example: executable scripts to initialize network interfaces.
I assume you mean the legacy ifup/ifdown scripts? The primary and default path is NetworkManager, instead. Or did you _want_ this done with shell scripts? Unclear from your post.