Conversation

Notices

1. Embed this notice
   Leah Rowe is not a Rowebot (libreleah@mas.to)'s status on Tuesday, 06-May-2025 19:29:55 JST Leah Rowe is not a Rowebot

   I've been on and off auditing lbmk (Libreboot's build system), greatly cleaning up the code.

   I'm not really doing it today, but I devised this change while caffeinated, and after consuming cheese and crackers:

   https://browse.libreboot.org/lbmk.git/commit/include/git.sh?id=e8be3fd1d41c3c0a81c2cfecb3fa68271ad794ca

   This is how you write in sh.

   fe_ and fx_ work around -exec limitations in find, for my use-case.

   See fe_ and fx_ functions:

   https://browse.libreboot.org/lbmk.git/tree/include/lib.sh?id=e8be3fd1d41c3c0a81c2cfecb3fa68271ad794ca#n146

   With fx/fe, I recursively git-am many git patches into upstream sources while cloning the repo. *1 line of sh.*

   • Embed this notice
     Leah Rowe is not a Rowebot (libreleah@mas.to)'s status on Wednesday, 07-May-2025 03:07:18 JST Leah Rowe is not a Rowebot

     in reply to

     Here is yet more example of the power of fe_ and fx_ functions in lbmk:

     https://browse.libreboot.org/lbmk.git/commit/?id=5686f35e0f1522d45361f042adc135b5782eae32

     Using them, I was able to reduce the size of the extract_intel_me_bruteforce() function in half. Reducing the sloccount by 18.

     Doing this kind of programming in sh isn't all that common but lbmk does all kinds of weird hacks like this.