On 6/24/21 11:56 AM, Giovanni Mascellani wrote:
What instead I think Debian (and Debian users) would much prefer is to avoid downloading binaries compiled from somewhere else than Debian build servers, like it happens now for gecko and mono. I don't know what are the reasons behind that choice, but I personally dislike it both as a user (because when I download packages from my distribution I expect to have stuff working without having to download other code from other places; downloading executable code requires trusting your peer, and one of the reasons of using a distribution is to put your trust in them and not having to question it again for any program you run) and as a developer (because I have to interact at runtime with my program to have it running the code I'm working on). I would really like to avoid adding FAudio to this dreaded list.
I think the reason is because of how huge the codebase of Wine Gecko and Wine Mono is, as well as how painful it would be to integrate to Wine build, both in term of integration and impact on Wine development.
Wine Mono is quite alright to build separately, but it's still a huge task, and although I think I've built a custom Wine Gecko once, it was such a pain that I'm not even sure I actually did or if it was just in my dreams.
Then I agree that it's pretty inconvenient to have them separate, and also not nice to distribute them through a side-channel.