New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build: make .tar.xz creation opt-out, fail if no xz #24551
Changes from all commits
File filter...
Jump to…
Diff settings
| @@ -810,13 +810,29 @@ BINARYNAME=$(TARNAME)-$(PLATFORM)-$(ARCH) | |||||
| endif | |||||
| BINARYTAR=$(BINARYNAME).tar | |||||
| # OSX doesn't have xz installed by default, http://macpkg.sourceforge.net/ | |||||
| XZ=$(shell which xz > /dev/null 2>&1; echo $$?) | |||||
| HAS_XZ ?= $(shell which xz > /dev/null 2>&1; [[ $$? = 0 ]] && echo 1 || echo 0) | |||||
| # Supply SKIP_XZ=1 to explicitly skip .tar.xz creation | |||||
| SKIP_XZ ?= 0 | |||||
|
This conversation was marked as resolved
by refack
rvagg
Author
Member
|
|||||
| ifeq ($(HAS_XZ) $(SKIP_XZ), 1 0) |
etc.
This comment has been minimized.
This comment has been minimized.
rvagg
Nov 22, 2018
Author
Member
I'm not concerned about churn, I'd rather aim for grokkability in Makefile since it's already full of magic. So is your suggestion that, with the check-xz as it is in this PR (i.e. with HAS_XZ and SKIP_XZ intact), that we roll up the blocks surrounding the xz call under the XZ boolean?
ifeq ($(HAS_XZ) $(SKIP_XZ), 1 0) is a little esoteric, so perhaps that'd be a good change for grokkability sake.
This comment has been minimized.
This comment has been minimized.
refack
Nov 22, 2018
Member
Yes. That "if" is very specific. If we restore XZ but now it's cumputed as ($(HAS_XZ) $(SKIP_XZ), 1 0) (even comment that it means "we have a working xz available") the lower code blocks will be simpler to grok.
Why not keep XZ as (pseudocode)
?