Re: policy proposition for javadoc installation
-----BEGIN PGP SIGNED MESSAGE-----
Guillaume Rousse <firstname.lastname@example.org> writes:
> We would like your opinion about this proposition:
> Package documentation usualy goes in a distinct subdirectory under
> /usr/share/doc, as established by FHS. Java software also comes with
> javadoc-generated api documentation, which is usually stored in a
> subdirectory with rest of documentation.
> We propose instead to install it under a distinct subdirectory under a new
> /usr/share/apidoc top-level directory. Advantages:
Why not /usr/share/javadoc ???
> - distinction with standard documentation
> - would allow to link generated javadoc versus already-installed one
There is no way to do this without re-running javadoc.
> - name 'apidoc' is not specificaly related to java, could also be used by
> other languages
Which is the problem.
What if I want to generate my API doc with different packages (doxygen, gjdoc,
javadoc), or even by hand.
Kevin A. Burton ( email@example.com, firstname.lastname@example.org, email@example.com )
Location - San Francisco, CA, Cell - 415.595.9965
Jabber - firstname.lastname@example.org, Web - http://relativity.yi.org/
My entire MP3 collection is here: http://relativity.yi.org/mp3. Have fun.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Get my public key at: http://relativity.yi.org/pgpkey.txt
-----END PGP SIGNATURE-----