diff options
| author |   Andrew Ammerlaan <andrewammerlaan@gentoo.org> | 2024-05-09 19:01:00 +0200 |
|---|---|---|
| committer | Andrew Ammerlaan <andrewammerlaan@gentoo.org> | 2024-05-17 14:06:46 +0200 |
| commit | 05ad18f837f89cfa2b20e01264ef6332c240072c (patch) | |
| tree | 63f695157043bb3d4cadc9b4943dfef9a9b55139 /dev-lang/elixir/elixir-1.14.5-r2.ebuild | |
| parent | sys-kernel/linux-firmware: add USE=dist-kernel (diff) | |
| download | gentoo-05ad18f837f89cfa2b20e01264ef6332c240072c.tar.gz gentoo-05ad18f837f89cfa2b20e01264ef6332c240072c.tar.bz2 gentoo-05ad18f837f89cfa2b20e01264ef6332c240072c.zip | |
linux-info.eclass: respect eselect kernel setting in binpkgs
Commit f51cd5b64c14ddfb83488a12d538c66a4a309376 resets kernel environment
variables when binpkgs are merged, this makes sense since we care about the
system that the binpkg will be installed on, not the system the binpkg was
built on. This introduced Bug 931213 as a side-effect, which will be fixed
in a separate commit to linux-mod-r1.eclass. In preparation of that, we document
and rename the LINUX_INFO_BINARY_RESET to SKIP_KERNEL_BINPKG_ENV_RESET.
However, commit f51cd5b64c14ddfb83488a12d538c66a4a309376 also makes binpkgs
always use the running kernel version. This behaviour is surprising and
confusing. In principle the 'eselect kernel' setting should still be respected
when binpkgs are used.
Bug: https://bugs.gentoo.org/926063
Bug: https://bugs.gentoo.org/931213
Signed-off-by: Andrew Ammerlaan <andrewammerlaan@gentoo.org>
Diffstat (limited to 'dev-lang/elixir/elixir-1.14.5-r2.ebuild')
0 files changed, 0 insertions, 0 deletions