I think GNU's gospel includes /etc.
https://www.gnu.org/prep/standards/html_node/Directory-Variables.html
If your program installs a large number of files into one of the
standard user-specified directories, it might be useful to group
them into a subdirectory particular to that program. If you do
this, you should write the install rule to create these
subdirectories.
I understand their point, but we could say the same thing about $(bindir)
and I don't think anyone is suggesting we default to installing all
of the executables in $(bindir)/nmh (unless maybe we are?).
I guess my real question is ... should this decision be made by a
packaging system, or should we enforce it always? I'm totally fine with
an nmh RPM/deb/BSD port/Homebrew recipe doing --sysconfir=/etc/nmh, or
whatever. What gives me pause is us enforcing that without giving the
user a chance to overrride it; that was the point of Steve Winikoff's
original email, and that was the change in behavior from 1.6 that I
don't think was really fully understood at the time it was implemented.
--Ken
--
Nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers