We have some set of packages (A) which collectively depend on one or..
more kernel options being set in specific ways, and the options need to REMAIN set if you want the packages to continue work.
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?
It would need to keep long-term state about which packages want
specific options set/unset/modular, as well as short-term state
about the config from each boot.
I wanted to break the prior thread to discuss the root issue.
We have some set of packages (A) which collectively depend on one or
more kernel options being set in specific ways, and the options need to REMAIN set if you want the packages to continue work.
There are also a subset of packages (B), usually kernel modules themselves that will outright fail to compile if specific options are/are not set.
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.
Ebuilds should be able to call the tool (but it could be made optionalCan 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 whereI'm not sure if I understand you correctly but if you mean not doing
the system that has package building isn't where the packages are being used.
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!)
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.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 60:13:09 |
Calls: | 6,654 |
Calls today: | 6 |
Files: | 12,200 |
Messages: | 5,331,392 |