-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Request] Interfere bypass and testing #80
Comments
Maybe... could exit Lines 2 to 37 in 90c3586
Then to build without interfere:
|
Can bypass by renaming folder. Still don't know a way to test interferes without committing. |
nvm 😬
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.)
The text was updated successfully, but these errors were encountered: