zlacker

I would trust a build coming from the upstream project more than individual build efforts by people outside the upstream. It usually make it more more organized and do help people who wants a quick trial ( I wouldn't like having to build each thing I want to try). Also people keeping up with updates is a problem when you provide the builds. Imagine having to keep up with manually build 20 software/packages every couple of weeks.

Yes, we know it is mot requirement. But it is nice and convention to do.

>>bluish+(OP)
If it's reproducible binaries though, and all the various build hashes match, what's the issue?

>>bluish+(OP)
I prefer builds from repositories I trust. Lots of stuff happily makes it into the Debian repos. So I guess I'm kind of the opposite.

>>tetris+v2
I think this sort of verification being available is exceedingly rare, especially for builds that statically link dependencies.

>>bluish+(OP)
I hope you don't use a Linux distribution then. 99% of packages of 99% of distros are built by the distro (or a parent, e.g., using Debian repos) and not the upstream source. In fact, getting builds directly from upstream is the exception rather than the norm, usually used for more niche software that isn't shipped by distros (although it is getting more prevalent with Flatpak).