> most of the packages come with "integrated documentation"

Does this include ocamldoc generated API documentation? It would be great if
this was available for all packages. For example, I do not find
documentation for the standard library.


On Mon, Nov 9, 2009 at 12:53 PM, Gerd Stolpmann <[email protected]>wrote:

>
> Am Montag, den 09.11.2009, 17:20 +0100 schrieb AUGER:
> > Hi all,
> > for instance, we have
> > *app
> > *conf
> > *godi
> > patckage types, but what about adding a
> > *doc
> > package type for ocamldoc generated documentation:
> >
> > compiling a documentation can take some time in one hand
> > a lot of packages don't have their own documentation (lablgtk2 for
> > instance),
> >
> > so installing or not a documentation is way too general to be done in
> each
> > configure script,
> > and many package managers provide them separately, so I think we should
> > offer doc packages
>
> There are a few manuals that are distributed separately, but most of the
> packages come with "integrated documentation" (and some, unfortunately,
> without, or there is only a web site). Either the docs are just a bunch
> of already generated files that only need to be copied to the right
> place, or they are generated on the fly with ocamldoc (sure, it is
> sometimes time-consuming).
>
> I don't see why the addition of a new category makes any of these things
> easier. Can you elaborate a bit more?
>
> Gerd
> --
> ------------------------------------------------------------
> Gerd Stolpmann, Bad Nauheimer Str.3, 64289 Darmstadt,Germany
> [email protected]          http://www.gerd-stolpmann.de
> Phone: +49-6151-153855                  Fax: +49-6151-997714
> ------------------------------------------------------------
>
> _______________________________________________
> Godi-list mailing list
> [email protected]
> https://godirepo.camlcity.org/mailman/listinfo/godi-list
>
_______________________________________________
Godi-list mailing list
[email protected]
https://godirepo.camlcity.org/mailman/listinfo/godi-list

Reply via email to