Open xiota opened 1 year ago
Maybe... could exit interference-apply()
early if a special file, like interfere.bypass
, is detected?
Then to build without interfere:
chaotic get package
touch package/interfere.bypass
chaotic mkd package
Can bypass by renaming folder. package_
and pkgbuild-package
have been suggested rename targets.
Still don't know a way to test interferes without committing.
It still seems like a handy feature to test out interferes.
This PR only allows bypassing interferes, and others (@PedroHLC @Technetium1) have pointed out alternative methods.
Still don't know a way to test new interferes that haven't yet been committed though.
Would be nice if there were a way to bypass (broken) interferes or to test a (not yet merged) interfere. When testing interferes, the package directory shouldn't be cleaned because the build is likely to be run multiple times. (This could also be useful for checking artifacts when debugging the PKGBUILD.)