Re: When to use update-alteratives
Steve Langasek <firstname.lastname@example.org> writes:
> 10.1. Binaries
> Two different packages must not install programs with different
> functionality but with the same filenames. (The case of two programs
> having the same functionality but different implementations is handled
> via "alternatives" or the "Conflicts" mechanism. See Section 3.10,
> So, it already *is* in a normative part of the document, it's just not
> necessarily presented in the best order for readers to consume it. :/
Aha, thanks. I *knew* I'd read it somewhere, but I'd fooled myself into
thinking I'd just read it in Appendix F.
In that case, a cross-reference from where update-alteratives is talked
about in 3.10 would be helpful, I think.
Russ Allbery (email@example.com) <http://www.eyrie.org/~eagle/>