Closed xiota closed 10 months ago
The purpose is to make it easier to tell that a package has a separate interfere. Then when there's a problem, I won't have to manually check multiple places for where to fix it.
Custom pkgbuilds would still be a problem.
Effect on end users should be minimal. Maybe some confusion about what purpose the extra package serves.
Doesn't seem to be working (optdep not being added). Any idea why?
It works when I manually copy/paste the part that's supposed to be added into a PKGBUILD.
Oh, if you deployed stuff already to test - we still need to deploy the changes to the builders. Ufscar already has been updated, Nix needs us to bump the inputs commit and rebuild the system, which I'm probably going to do tomorrow.
Thanks. Will wait until tomorrow.
Created package chaotic-aur/chaotic-interfere
. Should be impossible to install (without override).
An idea to make tracking interfered packages easier. Add an optdep on
chaotic-interfere
to interfered packages. Shouldn't affect building, and the following command would show a list of interfered packages in the repository (would need to create a dummy package):Not using:
depends
- interferes with build / install. However, would make visible in logs that an interfere was used.makedepends
- interferes with build / install, and not visible afterwards. Would be visible in logs. Maybe use in combination with optdep?pkgdesc
- difficult to cover all cases.