aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
* Rename get_current_kernel to get_selected_kernelWynn Wolf Arbor2020-06-04-3/+3
| | | | | | | | In a similar vein to commit 5f83bed ("Use consistent and explicit terminology in set_kernel()"), the term "current" kernel is ambiguous here. An upcoming commit will introduce the concept of the "running config", which is the kernel configuration the currently running kernel uses. To reduce any ambiguity, use "selected" instead of "current".
* Use OR lists instead of if commandsWynn Wolf Arbor2020-06-04-6/+2
| | | | | Use a more succinct and clear style in two places by converting if commands into simple OR lists.
* Mention the base template in kern.1Wynn Wolf Arbor2020-05-16-2/+3
| | | | | Since fragment merging will fail if the base template does not exist, make sure to mention it in the manual.
* Don't exit if newest kernel is selectedWynn Wolf Arbor2020-05-16-2/+7
| | | | | | It was really never a good idea to make this a fatal error, especially considering consecutive calls of kern(1) without any arguments will fail after the kernel has been set successfully once.
* Simplify conditional logic in test_diff()Wynn Wolf Arbor2020-05-16-7/+5
| | | | | | | | | | | | | | | | | Previously we recorded the return value of the sed ... | diff pipeline into a variable and later used it to test whether the command returned successfully or not. Since we enable errexit, this meant that the diff command failing would terminate the execution of the whole script. We are unsure how this was not caught earlier as the script has been in use for quite a while now - it is possible that bash 5.0 shows different behaviour here. It is our understanding that bash's current behaviour is correct, however. Instead of using a variable to store the return value, put the whole pipeline into an if clause, and react to its success or failure there. Whilst this does remove our ability to indicate diff's actual return value, it makes this test simpler and more straightforward.
* Add TODO item regarding /boot/config-* supportWynn Wolf Arbor2020-05-05-0/+2
|
* Add manuals to Makefile0.3.0Wynn Wolf Arbor2020-05-05-1/+3
|
* Use consistent and explicit terminology in set_kernel()Wynn Wolf Arbor2020-05-05-2/+2
| | | | | | | | | With the introduction of the manuals, we realized that the term "active kernel" is ambiguous. It might refer to both the currently selected kernel in eselect and the kernel the system is running on at the moment. Use "selected" instead of "active" to make this more explicit and line it up with the usage in the manual.
* Add kern(1) and kernfrag(7) manualsWynn Wolf Arbor2020-05-05-0/+281
|
* Remove && from all()0.2.0Wynn Wolf Arbor2020-03-23-7/+7
| | | | | Since the script uses the `set -e' option, chaining together commands with && will fully negate its effects.
* Exit if the kernfrag directory is inaccessibleWynn Wolf Arbor2020-03-23-0/+4
|
* Check whether /boot is already mountedWynn Wolf Arbor2020-03-23-1/+5
| | | | | | | This commit adds code to check whether /boot is mounted or not, and will skip the mount command if the path is already mounted. This will fix an issue where the script exited prematurely if /boot was already present, as the mount command failed and we use `set -e'.
* Add a prompt to test_diff instead of exiting unconditionallyWynn Wolf Arbor2020-03-16-1/+5
| | | | | | For differences in config files that can safely be ignored, introduce the possibility of continuing with the build and install instead of exiting unconditionally.
* Hide potential warning about broken symlinkWynn Wolf Arbor2020-03-16-1/+1
| | | | | | | If the user removes the old kernel sources whilst still having the symlink point to the kernel directory, eselect will issue a warning about an invalid kernel target. For the purposes of kern, we can safely ignore this warning.
* Initial import0.1.0Wynn Wolf Arbor2020-02-29-0/+137
powered by cgit and git | oriole.systems | how to verify signatures