I used to use that approach, but found in the last several years more than half the web sites I use reject email addresses with “+” characters.
I even use several sites that used to take those addresses just fine now reject them. That made me wonder if some common JS package for parsing email addresses got changed.
Again, less than half of RHEL is even software released under the GPL.
I would be completely shocked if this were true. I'm calling BS here.
I used to be my company's primary contact for our Red Hat TAM for almost 13 years. Our TAMs were very proud to claim that all of RHEL was FOSS software, licensed under the GPL or sometimes other FOSS licenses.
I spun up a RHEL 9.2 instance and ran:
$ sudo dnf list --all | wc -l
6671
$ dnf info --all | grep "^License .*:.*GPL.*" | wc -l
4344
$ python -c "print(4344/6673 * 100)"
65.11767351221705
So 65% of RHEL 9's packages are under a GPL license.
Much of the software that is GPL was authored by Red Hat themselves. According to the text of the GPL itself, Red Hat is not required to distribute the code to the totality of the RHEL distribution or even to more than half the code.
Half?!? Again, where are these mysterious numbers coming from?
It doesn't matter if Red Hat authored those packages or not. What matters is if they were distributed under a GPL license. If you're claiming that Red Hat multi-licensed those GPL'd packages that they exclusively wrote so they don't have to comply with the GPL, please point those out to me (or at least a few), so I can check them out.
To solve your DRY problem, you may not realize that you can generate target rules from built-in functions eval and foreach and a user-defined new-line macro. Think of it like a preprocessor step.
For example:
# This defines a new-line macro. It must have two blank lines.
define nl
endef
# Generate two rules for ansible playbooks:
$(eval $(foreach v,1 2,\
.PHONY : ansible.run-playbook$v $(nl)\
\
ansible.run-playbook$v : ensure-variables cleanup-residue | $$(ansible.venv)$(nl)\
ansible.run-playbook$v :;\
... $(nl)\
))
I winged it a bit for you, but hopefully I got it right, or at least right enough you get what I'm doing with this technique.
You may like an approach I came up with some time ago.
In my included file that's common among my Makefiles:
# Ensure the macro named is set to a non-empty value.
varchk_call = $(if $($(1)),,$(error $(1) is not set from calling environment))
# Ensure all the macros named in the list are set to a non-empty value.
varchklist_call = $(foreach v,$(1),$(call varchk_call,$v))
At the top of a Makefile that I want to ensure certain variables are set before it runs:
$(call varchklist_call,\
INSTDIR \
PACKAGE \
RELEASE \
VERSION)
I usually do these checks in sub-Makefiles to ensure someone didn't break the top level Makefile by not passing down a required macro.
I’ve done both. I wrote my own scripts to generate the WG config files to handle variations in configure I needed to make for my different networks (masking, IPv6, cross multiple WG networks).
After converting to Tailscale, WG is just an extra level of hassle I can now easily avoid.
Use Tailscale. Much easier to configure and manage than raw WireGuard.
The GPL only cares about ensuring the four freedoms are maintained for binaries and their related sources.
No, the GPL goes beyond that. It not only ensures those four freedoms, but also ensures the freedom to exercise them without restriction. That's what the language in section 6 is meant to protect. If RH only limited potential access to future releases of binaries, I see that as fine and not a restriction. But RH is going well beyond that by terminating existing contracts; accounts; technical, web, and support access; and not refunding monies paid in advance for those services. (Theoretically, since they haven't done it to anyone yet that I'm aware of.) If legally those actions are not deemed a "restriction", then I'd agree with you.
Unless their board approves an earlier date.