diff options
| author | dann frazier <dann.frazier@canonical.com> | 2019-05-06 13:38:07 -0600 |
|---|---|---|
| committer | dann frazier <dann.frazier@canonical.com> | 2019-05-06 13:50:24 -0600 |
| commit | a42739719fb434aab308a3de97242a6be148ceb1 (patch) | |
| tree | 97a1e911e98a21862ea8cc400aa3f1a8c6875bc9 /debian/rules | |
| parent | 99990d2175d6e5bccf6cd7c35fdba61461e985f7 (diff) | |
| download | efi-boot-shim-a42739719fb434aab308a3de97242a6be148ceb1.tar.gz efi-boot-shim-a42739719fb434aab308a3de97242a6be148ceb1.zip | |
Require dbx hashes
While it maybe convenient for a developer to be able to do a build
w/o any dbx hashes, it prevents the $(DBX_LIST) target from having
a proper dependency on the $(DBX_HASHES) file. If a developer were
to add a new hash in a built tree, make would not detect that on
a subsequent build and would not update the $(DBX_LIST) file.
Continue to support a NULL $(DBX_LIST) build by touching the
$(DBX_LIST) file in case no efisiglist commands ran. Developers
can now create an empty $(DBX_HASHES) file to get that.
Diffstat (limited to 'debian/rules')
| -rwxr-xr-x | debian/rules | 17 |
1 files changed, 8 insertions, 9 deletions
diff --git a/debian/rules b/debian/rules index d898d7aa..8527f82a 100755 --- a/debian/rules +++ b/debian/rules @@ -43,15 +43,14 @@ COMMON_OPTIONS += \ CC=$(DEB_HOST_GNU_TYPE)-gcc-7 \ $(NULL) -$(DBX_LIST): - if [ -f ${DBX_HASHES} ]; then \ - set -e; \ - for HASH in $$(grep -E [[:xdigit:]]{32} ${DBX_HASHES}); do \ - efisiglist -o $@ -a -h $$HASH; \ - done; \ - else \ - touch $@; \ - fi +$(DBX_LIST): $(DBX_HASHES) + rm -f $@ + set -e; \ + for HASH in $$(grep -E [[:xdigit:]]{32} $<); do \ + efisiglist -o $@ -a -h $$HASH; \ + done + # Support an empty $(DBX_HASHES) + touch $@ %: dh $@ --parallel |