-
Notifications
You must be signed in to change notification settings - Fork 4
Description
build-wrap
supports an allow.txt
configuration file, which effectively disables build-wrap
for a dependency:
https://github.com/trailofbits/build-wrap?tab=readme-ov-file#homeconfigbuild-wrapallowtxt
However, this has turned out to be not convenient enough. From my own experience, I often don't want to figure out which dependency is causing build-wrap
to fail. So I disable build-wrap
altogether and then forget to reenable it. A better solution would allow build-wrap
to be disabled for a directory rather than system wide.
So I am proposing to create a $HOME/.config/build-wrap/config.toml
file, which would take precedence over allow.txt
.
The new file would contain entries like this:
[allow]
directories = ["..."]
packages = ["..."]
Or this:
[ignore]
directories = ["..."]
packages = ["..."]
The reason for both [allow]
and [ignore]
is that I cannot decide which I prefer.
Note that I am currently going with "packages" over "dependencies" because one might expect the latter to include versions, e.g., [email protected]
. Perhaps this could be a future enhancement.