Randy McMurchy wrote: > go moko wrote these words on 01/20/06 15:04 CST: > > >>For some packages of the book, all the doc is >>explicitely installed in >>/usr/share/doc/<package-name>-<version>. >>But for others, like Pango or ATK, the --with-html-dir >>tag of configure is not used for this in the book's >>commands, and so, the doc isn't versionned. >> >>I know it's a detail, and that users can do >>'./configure --help' to find this, and that doc can be >>put where one wants to, but perhaps a note added after >>the command could be a good option. What do you think? > > > I tend to disagree with you. Because this is not your typical > documentation, but instead it is the API documentation produced > by GTK-Doc, it goes into the /usr/share/gtk-doc hierarchy. > > I think this is correct. Just my opinion, and others may think > different. We'll see what others say. However, keep in mind > that I have over 60 packages that have installed under the > .../share/gtk-doc hierarchy. > > For example the only documentation I see for Pango (except for > one man page) is located in /usr/share/gtk-doc/html/pango. Is > it worth changing all the package instructions to point this > documentation somewhere else? > > Docs produced by gtk-doc have been going in .../share/gtk-doc > for a *long* time.
I agree with Randy. API documentation is pretty specialized. Programmers can find it if they need to. Its not something everybody looks at. Moving the files are far more effort than its worth. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
