Closed issue by mhmdanas on void-packages repository

https://github.com/void-linux/void-packages/issues/45507

Description:
<!--
  if you are creating a bug report or package request, please fill out one of the forms here:
  https://github.com/void-linux/void-packages/issues/new/choose

  Don't request an update of a package, We have a script for that:
  https://repo-default.voidlinux.org/void-updates/void-updates.txt
  However, a quality pull request may help.
-->

When a `vsed` doesn't apply, they currently print a warning by default, and the build goes on. This can hide potential issues. `xbps-src` does have an `-s` flag, which in that case causes the build to stop at the failing vsed. This flag _is_ passed in the CI, but large PRs skip CI and so authors of those PRs may never notice the now-outdated `vsed`s (see e.g. https://github.com/void-linux/void-packages/issues/42441). Therefore, I propose enabling the "strict" `vsed` behavior by default, and would even go so far as to suggest removing the non-strict behavior, because I honestly don't see its point.