installation directories for docs

installation directories for docs

[Ralf Wildenhues]

The autotools update changed a couple of default installation
directories as well as a few switches to pick them.

The GNU Coding Standards, Autoconf, and toplevel `./configure --help'
specify
  ${datarootdir}/doc/${PACKAGE}

as default for docdir.  However, toplevel and gcc/ leave PACKAGE empty,
so that it ends up being
  ${datarootdir}/doc/

instead, which is also what gcc/doc/install.texi currently documents.
Also, some of the other parts of the GCC tree have nonempty
PACKAGE, leading to different installation directories; see
<http://gcc.gnu.org/ml/gcc-patches/2009-08/msg00842.html> and
<http://gcc.gnu.org/ml/gcc-patches/2009-08/msg00935.html>.

In <http://gcc.gnu.org/ml/gcc-patches/2009-09/msg01598.html>, I proposed
a patch for changes.html, but that would require cleaning up the
implementation first.


Should we set PACKAGE in libgomp and libiberty, to 'libgomp' and
'libiberty' respectively, and thus have the GCC part of the tree more or
less uniform?  Or should that be 'gcc' in both cases?

We can set 'PACKAGE = gcc' in gcc/Makefile.in easily, which would allow
  ./configure --docdir='${datarootdir}/${PACKAGE}-${PKGVERSION}'

but setting PACKAGE in the toplevel is problematic due to sync with src.

Also, do we want overrides like --pdfdir=/foo to install all PDF files
below /foo/*.pdf (as GCS suggest) or go with /foo/gcc/*.pdf,
/foo/libgomp/libgomp.pdf etc.?

For now, below also lists 'psdir' but toplevel doesn't allow 'make ps'.
Change the documentation or implement the 'ps' target?

Also, GCS document install-dvi and install-ps, both of which are
currently not supported.  Are they desirable to have?

Thanks,
Ralf

Re: installation directories for docs

[Joseph S. Myers]

On Sun, 11 Oct 2009, Ralf Wildenhues wrote:

> Should we set PACKAGE in libgomp and libiberty, to 'libgomp' and
> 'libiberty' respectively, and thus have the GCC part of the tree more or
> less uniform?  Or should that be 'gcc' in both cases?

I think it should be "gcc" - though when libiberty is installed as part of 
a binutils installation, it should there be "binutils", or as part of a 
GDB installation, "gdb".  Getting everything other than libiberty right 
may be easier than making libiberty act appropriately depending on what 
package is being installed.

Directories should not have ".html" suffixes, though as you have noted 
some in binutils do.

> Also, do we want overrides like --pdfdir=/foo to install all PDF files
> below /foo/*.pdf (as GCS suggest) or go with /foo/gcc/*.pdf,
> /foo/libgomp/libgomp.pdf etc.?

I think following GCS is appropriate.

> For now, below also lists 'psdir' but toplevel doesn't allow 'make ps'.
> Change the documentation or implement the 'ps' target?
> 
> Also, GCS document install-dvi and install-ps, both of which are
> currently not supported.  Are they desirable to have?

If someone wants them, I see no problem with having them implemented for 
GCC and src (unlike "dist" or "uninstall").

-- 
Joseph S. Myers
joseph@codesourcery.com