Jeff King wrote: > The worst case is just making things slightly more inconvenient for > Git developers on older systems, because because they might have to > install an updated gem rather than using the system package (you > sometimes can end up in dependency hell for a gem upgrade with > versions of ruby, system libraries, etc, but I haven't found > asciidoctor particularly needy in that respect). The asciidoctor gem has *zero* dependencies. If you end up in a dependency hell, it wasn't the fault of asciidoctor, and it won't be affected. I've been using Ruby for at least 15 years, and I've never found myself in a dependency hell, so it would be interesting to see how anybody could end up there. Sometimes the mix between system and user gems is confusing, but they work fine. I wouldn't call that a "dependency hell". And of course you can always just `rm -r $GEM_HOME` and start fresh. Most gems install rather quickly. -- Felipe Contreras
