In regards to the point in the binary build stage sequence at which your new code executes the efi script, and the below quoted comment besides it, I'm curious about what exactly you are worried about that prompted it?
"After includes/hooks because it copies in efi.img files that can be overriden by binary_includes and modified by binary_hooks" Do you have examples of existing hooks/includes which actually clash with the new files? Or are you simply worried about a user adding an include/hook which overwrites/deletes a file and thus breaks their image? If the latter, then I really don't agree that it's an issue. The includes and hooks scripts are there to allow last minute customisations before compiling the image, and if a user foolishly misuses them to break their image, then that's on them. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
