| ... | ... | @@ -128,12 +128,12 @@ Stuff not yet or barely started, to investigate, to consider, whatever: |
|
|
|
- [ ] Consider locking of `lb clean` and `lb config`. `lb config` does not use the lock at all, and so can be run in the middle of a build. `lb clean` is similar, it just deletes the lock early on (which may be useful for recovery purposes, but allows running during build).
|
|
|
|
|
|
|
|
Additionally, helping derivative distros somewhat:
|
|
|
|
- [x] I've submitted some MRs previously for Kali to help tweak the booloaders menus to properly benefit from the bootloader improvements work. I think these were merged, but I should review things when the bootloader changes are completely finalised considering that Raphaël reorganised some things.
|
|
|
|
- [x] I've submitted some MRs previously for Kali to help tweak the bootloaders menus to properly benefit from the bootloader improvements work. I think these were merged, but I should review things when the bootloader changes are completely finalised considering that Raphaël reorganised some things.
|
|
|
|
- [ ] I've noticed that Tails is stuck using live-build version 2.x, with custom hacks to get EFI support. They attempted a migration to v4.x some time ago, but after doing the work found that they experienced boot failure. I hope to try to assist them in migration to a newer version at some point if they need help.
|
|
|
|
|
|
|
|
Avoiding?
|
|
|
|
---------
|
|
|
|
Stuff I'm probabaly not going to try.
|
|
|
|
Stuff I'm probably not going to try.
|
|
|
|
|
|
|
|
- Long ago there was a plan to convert live-build to python. This was actually started then reverted and never reattempted. Back in 2015 I thought it might be nice to try to get it accomplished, as an exercise to become more familiar with python (which I've not had much opportunity to work with), and considering how brittle shell code can be. I never got anywhere near starting that. Now, it still might be nice, however especially considering all the work above already on my list, and not having unlimited time and resources, I'm doubtful about whether I'd be able to do it. Most significantly though even if I could find the time, I suspect that the team might not have the appetite for this in terms of the effort to review, if they even agreed with it being a nice idea.
|
|
|
|
- The whole build is done with elevated privileges. Could it not be possible to drop privileges when not needed. I thought a little about this but it might not be at all easy in shell code, and also given directory permissions for instance, it might not be feasible at all. (There is also bug [#788764](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788764) about this topic).
|
| ... | ... | |
