On Mon, Sep 27, 2021 at 11:47:38PM +0200, Michał Górny wrote: > > Can we consider moving the checks for set A somewhere else, such that we > > don't check the kernel config during package compile & install time, but > > only check it later? This also meaningfully resolves that cases where > > the system that has package building isn't where the packages are being > > used. > I'm not sure if I understand you correctly but if you mean not doing > checks before compiling/installing, then I have to disagree. There is > value in knowing about this kind of problems early (hey, that's why we > have pkg_pretend in the first place!) Ebuilds should be able to call the tool (but it could be made optional easily), which does the checks MORE efficiently than the present eclass code. The ebuilds would be responsible for suitable warnings or failures based on the tool's output.
E.g. maybe you're in a rescue environment and you know the tooling will work fine on your final environment. > There's certainly value in knowing 'I need to rebuild my kernel' early > vs learning only after you've spent significant time waiting for some > package to build. One thing to this is if you're doing pkg_pretend for multiple packages in a single emerge call, the tool could greatly amortize the cost of the checks, as well as having them available after merge. Great thought I had would be this tool could ALSO run on boot and warn if some packages are unlikely to work -- Robin Hugh Johnson Gentoo Linux: Dev, Infra Lead, Foundation Treasurer E-Mail : robb...@gentoo.org GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136
signature.asc
Description: PGP signature
