Am 2020-08-24 15:24, schrieb Nathan Willis:
I don't understand the strong reaction here. I'm merely asking a question.
Well, that wasn't meant as a "strong reaction", sorry, it was merely an exclamation mark emphasising me asking you not to introduce this kind of complexity into font packages. Sorry if it came over differently.
In what way is conflicting packages a better approach? Would that not risk introducing conflicting dependency sets from other packages? Possibly even deeply nested ones?
update-alternatives should probably not get used for packages for which it usually makes no sense to have both installed at the same time anyway. Also, it's a command line tool and rather clumsy to work with, so this adds complexity to the user. And, setting it up to provide a choice between a single font file and a set of font files is probably also rather tricky for the maintainer. So, all in all, it just adds complexity. Having two packages conflict each other and having one provide the other so dependencies are fulfilled is a lot easier to work with in comparison.
- Fabian