Junio C Hamano <gits...@pobox.com> writes:
> Jiang Xin <worldhello....@gmail.com> writes:
>> Html documents will be installed to root dir (/) no matter what prefix
>> is set, if run these commands before `make` and `make install-html`:
>> $ make configure
>> $ ./configure --prefix=<PREFIX>
>> After the installation, all the html documents will copy to rootdir (/),
>> $ git --html-path
>> $ git help -w something
>> fatal: '<PREFIX>': not a documentation directory.
> I am not sure if this description is correct. The generated configure
> seems to set
> so it is likely you would get not <PREFIX> but <PREFIX>/share, no?
This was a mis-diag; without docdir mentioned in config.mak.in, we
do not even get that far, and htmldir will end up being empty, and
the runtime code adds <PREFIX> to it in system_path(). What I was
describing was what happens when you only mention @docdir@ but not
PACKAGE_TARNAME in the file.
> And the worst part is that having to know that the file needs to
> export docdir and PACKAGE_TARNAME feels to me that we are tying
> ourselves to too much detail in the internal implementation detail
> of versions of autoconf we happen to have for testing this change.
This still stands. It really feels wrong that this file has to be
aware of such an implementation detail of autoconf. But as an
interim workaround, setting these two otherwise unused variables may
be the best we could do.
I am not sure if such a layout can be actually used for installing,
though. Didn't we see some issues around the relativeness of
htmldir and mandir vs passing them down to Documentation/Makefile,
or is it not an issue when ./configure and config.mak.autogen is
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html