Summary: | FEATURES=getbinpkg can not be overriden in /etc/portage/package.env | ||
---|---|---|---|
Product: | Portage Development | Reporter: | catageek |
Component: | Binary packages support | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | Adrian.Bassett, bes.internal, cafaia, eschwartz93, fedeliallalinea, flexibeast, jbut, leho, leonchik1976, m_gentoobug, sam, son, sos, stoffepojken |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=705602 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 337456 | ||
Bug Blocks: | 377365, 924772 |
Description
catageek
2013-03-31 07:01:51 UTC
Currently, FEATURES=getbinpkg only works as a global setting. There are other FEATURES settings that can be successfully overridden via package.env, such as buildpkg, splitdebug, and installsources. (In reply to Zac Medico from comment #1) > Currently, FEATURES=getbinpkg only works as a global setting. There are > other FEATURES settings that can be successfully overridden via package.env, > such as buildpkg, splitdebug, and installsources. What about PYTHON_SINGLE_TARGET? Are there any plans to change that behaviour? I'd really like to make use of that feature for that mighty libreoffice package that should not be compiled on my old & weak laptops ... Current issue comlicates the using of binary package hosting [1] setup for individual packages. [1]: https://dilfridge.blogspot.com/2021/09/experimental-binary-gentoo-package.html From a recent discussion: 2023-12-29 08:51:43 AM +ztrawhcse I did however note in locally playing around that it doesn't seem possible to set FEATURES=-getbinpkg in package.env 2023-12-29 08:51:59 AM +ztrawhcse so it's not fully clear how to guarantee a specific package is locally compiled 2023-12-29 08:52:08 AM @sam_ yes, this is an interesting question 2023-12-29 08:52:25 AM @sam_ overall package.env support is way harder if we allow it for any atom because getbinpkg affects dependency resolution 2023-12-29 08:52:36 AM @sam_ but supporting it to say i want a binpkg/not for a package overall is probably more doable 2023-12-29 08:54:55 AM +ztrawhcse possibly slot as well although I don't personally need slot support for this I would suspect that people only really have a use case for this at the cat/pkg level anyway, so limiting it to this is probably fine. 1. I always need to disable a binary package if I have a patch in `/etc/portage/patches/` for package. I would like this to happen automatically with a warning on emerge why this happened in addition to existing information. 2. Consider disabling the binary package via enabling use-flag somethign like `nobinpkg` then fetature binpkg-respect-use will work right now |