Re: [PATCH 4/7] docs: exclude documentation for commands that have been excluded
- Date: Mon, 15 Apr 2019 12:09:58 +0900
- From: Junio C Hamano <gitster@xxxxxxxxx>
- Subject: Re: [PATCH 4/7] docs: exclude documentation for commands that have been excluded
Eric Sunshine <sunshine@xxxxxxxxxxxxxx> writes:
>> diff --git a/Makefile b/Makefile
>> @@ -2455,22 +2455,25 @@ $(VCSSVN_LIB): $(VCSSVN_OBJS)
>> +Documentation/GIT-EXCLUDED-PROGRAMS: Makefile config.mak.uname
>> + $(QUIET_GEN)echo "EXCLUDED_PROGRAMS := $(EXCLUDED_PROGRAMS)" >$@
> Should this rule also have a dependency upon "config.mak.autogen"?
That is probably a good point.
> Perhaps like this:
> Documentation/GIT-EXCLUDED-PROGRAMS: Makefile $(wildcard config.mak*)
I'd rather not let changes to "config.mak-", which I keep in my
working tree (untracked and disabled copy of config.mak, that can be
readily activated by renaming), be part of dependency rules.
If we know 'autogen' is the only dependency that optionally can
exist, then depending explicitly on $(wildcard config.mak.autogen)
would be a better alternative. To those who do not use the autoconf,
the macro will expand to an empty string, and to those who do have the
path on the filesystem, the macro parrots the constant string it was
given, which is exactly what we want.