git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 0/3] Fix installation paths with "make install-doc"

From
John Keeping <john@keeping.me.uk>
Date
Feb 12, 2013, 23:00 UTC
Message-ID
<20130212230034.GA22779@river>
In-Reply-To
<7vmwv9ducx.fsf@alter.siamese.dyndns.org>
On Tue, Feb 12, 2013 at 02:45:34PM -0800, Junio C Hamano wrote:
Show 20 quoted lines
> Jonathan Nieder <jrnieder@gmail.com> writes:
> 
> > John Keeping wrote:
> >
> >>   Documentation/Makefile: fix inherited {html,info,man}dir
> >
> > This doesn't seem to have hit the list.
> 
> More importantly, 
> 
> >> When using the top-level install-doc target the html, info and man
> >> target directories are inherited from the top-level Makefile by the
> >> documentation Makefile as relative paths, which is not expected and
> >> results in the files being installed in an unexpected location.
> 
> I am not sure what problem it is trying to address.  During every
> cycle "make doc && make install-man install-html" is run for all
> integration branches and it didn't cause any problems.
> 
> A wild guess.  John, are you using config.mak.autogen?
Close - plain config.mak.

I set $prefix there and ran "make install-doc". That installed the man pages in Documentation/share/man/ in my Git source directory.

Show 17 quoted lines
> I _think_ exporting mandir/html/infodir from the top-level Makefile
> is wrong to begin with.  We should drop the "export mandir" from
> there.
> 
> Giving them unusual meaning (e.g. "mandir = share/man") is already
> bad and that needs to be fixed by limiting this "oh, on some
> platforms we compile-in GIT_MAN_PATH as a relative path to an
> unspecified place" insanity only to where -DGIT_MAN_PATH=<path> is
> defined.  The path used there does not help the building and
> installation of the documentation at all, so the variable used for
> the purpose of giving that <path> should not be named the same way
> as the variable used on Documentation/Makefile to name the real path
> in the first place.
> 
> Perhaps rename these to runtime_{man,html,info}dir or something and
> make sure {man,html,info}dir are defined as the real paths whose
> default values begin with $(prefix)?

Would it be sensible to define the values for these variables (with absolute paths) in a separate top-level file like config.mak.uname (defaults.mak maybe?) and include that in both Documentation/Makefile and Makefile, then calculate the relative path from $(prefix) to $({man,html,info}dir) for the compiled-in values.

John
Previous: Junio C Hamano
Message 20 of 20 in “Fix installation paths with "make install-doc"”
  1. 0/3 Fix installation paths with "make install-doc"John Keeping, Feb 12, 2013
  2. 1/3 Documentation/Makefile: fix spaces around assignmentsJohn Keeping, Feb 12, 2013
  3. Jonathan NiederFeb 12, 2013
  4. 2/3 Documentation/Makefile: move infodir to be with other '*dir'sJohn Keeping, Feb 12, 2013
  5. Jonathan NiederFeb 12, 2013
  6. John KeepingFeb 12, 2013
  7. 3/3 Documentation/Makefile: fix inherited {html,info,man}dirJohn Keeping, Feb 12, 2013
  8. Jonathan NiederFeb 12, 2013
  9. John KeepingFeb 12, 2013
  10. Jonathan NiederFeb 12, 2013
  11. Junio C HamanoFeb 12, 2013
  12. Junio C HamanoFeb 12, 2013
  13. John KeepingFeb 12, 2013
  14. Junio C HamanoFeb 12, 2013
  15. Makefile: do not export mandir/htmldir/infodirJunio C Hamano, Feb 12, 2013
  16. Jonathan NiederFeb 12, 2013
  17. John KeepingFeb 12, 2013
  18. Makefile: make mandir, htmldir and infodir absoluteJohn Keeping, Feb 24, 2013
  19. Junio C HamanoFeb 25, 2013
  20. John KeepingFeb 12, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.