My setup consist of a generic binhost with FEATURES=getbinpkg which is very helpful in general, but when I need to apply a user patch for a given package portage fetches the binary package instead of applying the patch and building. Of course for this specific case I used --usepkg-exclude, but it have some problems: 1- People that previously didn't have any binhost configured and decide to use a binhost may expect that their local patches are applied as usual, but instead when upgrading @world as usual their patches will be ignored by default, with in my opinion is not a very sane default. 2- Some users can have an overlay, for example for llvm+musl, in which they add patches for packages that need them for whatever reason. Those users as well may want to take advantage of a generic binhost for the majority of packages that doesn't require any specific patches. 3- And probably the least important issue: it's a little bit harder and more prone to errors if, for each package that a user wants to patch, it's required to add more flags to portage to exclude each single package for which packages are applied. If a patch is removed, then it would also be required to update the command/script accordingly, which is a little bit annoying. It would be nice if portage can get smart enough to automatically ignore the binpkg of a specific package if this package has applicable local user patches. Another option could be to ignore binpkgs if the ebuild/overlay doesn't match the ebuild/overlay used for creating the binpkg. Thank you very much Reproducible: Always
