|
Well, none that I've seen. Some of them make perfect sense (e.g., image processing libraries, etc), while others show up as recursive dependencies. In my experience, people don't write up lists of dependencies, especially since some are recursive. Instead, they look at the available tools and libraries, determining which are useful for their purposes. I'm not picking on Emacs (though its earlier icon as an overflowing kitchen sink gives a clue). This is a phenomenon of lots of software. If I want to use Asciidoctor-pdf, I must install Ruby, for example. The very fact that we have a wide variety of tools, languages, and libraries guarantees this sort of explosion. I'm as guilty as anyone of this, as my preferred language is Scheme. So if you want my programs, you have to install a compatible Scheme system. My real point here is that, given our understanding of dependencies, this sort of explosion is inevitable. So if I had a perfect, svelte Linux system, it would start picking up cruft almost from the moment it was created. That's just where we're at. |