Please can someone document how update-alternatives works with our d:l:r:e gem packaging strategy, and also *why* we are using it? I heard good explanations already (thanks darix), so personally I am now convinced (even though my tired brain already forgot some of the details), but other people have a right to know too.
Previously I had to rely on a combination of guesswork and pestering busy people, and this approach does not scale. It's not enough to say "just use gem2rpm", because guess what ;) things go wrong, and then it's really hard to debug without fully understanding the design. Also, it's not a real policy until it's documented. Yes it's an annoying / boring up-front cost, but the break-even will be quick. I suggest https://en.opensuse.org/openSUSE:Packaging_Ruby as a suitable location. Thanks a lot in advance! -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
