> you're ultimately interacting with a a layer on top of what the original package was designed to do This is fundamentally necessary, because the "original pa

> you're ultimately interacting with a a layer on top of what the original package was designed to do This is fundamentally necessary, because the "original package" (for some value of "package") doesn't care about anything else on the system apart from getting itself running using whatever arbitrary configuration scheme / fs layout / daemon management happens to please the upstream author.