Summary: | sys-apps/portage: support package.buildpkg configuration file | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Zac Medico <zmedico> |
Component: | Binary packages support | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | zerochaos |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=777624 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Zac Medico
2021-03-22 03:07:33 UTC
I like this idea as well, but to be clear, it's fine grained control over the packages I don't want binpkgs for which is lacking. Right now I add a list of things to EMERGE_DEFAULT_OPTS to exclude binpkgs from being built or used, it would be great if that was a file where I could exclude things. One possibility could perhaps be to patch --buildpkg-exclude to accept package sets as well as individual atoms? |