> you have all the work of doing that yourself There is a difference between unnecessary work and necessary work. When you take in a dependency, you become dep

> you have all the work of doing that yourself There is a difference between unnecessary work and necessary work. When you take in a dependency, you become dependent on it. That is necessary work. It's great to highlight that dependencies always mean work. There's probably some deeper truth to that, at least in what I do. But that doesn't mean all work is bad. After all, work is what we put in to make things, well, work. I "maintain" a bunch of fixes (that is, forks) of upstream stuff that I use all around the place. I used to maintain a few packages just for recreation. I have selinux dependencies, ansible playbooks, system accounts, certificates, and a lot of other stuff that I need to maintain in order to make stuff work. I guess I wanted to say don't be afraid to maintain your dependencies. Sure, it's work, but not unnecessary work.