Re: API docs locations

[Malcolm Tredinnick <malcolm commsecure com au>]

On Sun, Sep 02, 2001 at 07:58:42PM -0400, Havoc Pennington wrote:
> "R.I.P. Deaddog" <maddog linuxhall org> writes:
> > However, under the perspective of packagers,
> > /usr/share/doc/packagename-version/html can be a very bad choice, since
> > %doc will install various docs there. I'm not sure about Redhat and Debian,
> > but for Mandrake docs, %doc directory will be 'rm -rf'ed before placing
> > any docs there, thus losing all API docs.
> > 
> 
> Red Hat probably does this too, but it seems pretty dumb if we can't
> put real docs in /usr/share/doc. We could ideally do some RPM fixage
> or come up with a hack for this. I'll ask the RPM experts.

I must be missing something obvious here, so feel free to apply the
cluestick at will...

If I'm on an RPM based system, I will build rpms of the packages I want
to install. The api-docs would then be part of the -devel package (they
don't really make sense without the header files and stuff) and could be
installed in /usr/share/doc/glib-devel/, etc. If I install a new -devel
package, I get new docs.

If I'm building from tarballs and not wanting to make a package, then
surely I must be able to pass in a new prefix for the docs anyway
(enforcing a single location regardless of other prefixes seems a bit
dumb), so there's no conflict there.

So what's the catch?

Malcolm

-- 
Preserve wildlife. Pickle a duck.