I was building BerkeleyDB (4.7, yes I know, there are more recent versions available) on a Solaris machine. First try was to unpack, cd into the directory, run configure. It failed, there is no configure script. Bah. 🙁
Second try: searching for docs… found some… in HTML (the README refers to it and tells nothing else). This is a remote machine, I do not want to use a HTML browser remotely (I may not even have one installed there…). Bah. 🙁
Ok, dist/configure exists, no special options needed for my case, it seems.
There is even a Solaris specific HTML file, but from a quick glance at it with ‘less’, it looks like a FAQ.
Usability from a command line: zero.
Possibility to compile from a GUI (unix): I doubt it.
What is wrong with plain text files? If I download the source and want to compile it (and for Solaris this is the normal way of working), why the hell do I need some GUI instead of getting a plain text file with the required description (which is not graphically enhanced in the HTML version either)? You can even generate a plain text version of the docs automatically during the src-packaging process.
Hey Oracle, there is room for improvement here!
Seems that I will actively mentor again in this Google Summer of Code (as opposed to just review the submissions from students and/or acting as a fall-back mentor).
The project I will mentor is the “Make optional kernel subsystems register themselves via sysctl”-one from the FreeBSD ideas page.
The student already got into contact with me and it looks like he is motivated (he is already subscribed to several FreeBSD mailinglists, which is not a requirement we have in our GSoC docs).
I committed my patch for tools/kerneldoc/subsys. Except for not generating the PDF part, this is now the same config which I use to generate the online version. While writing the commit log I noticed that I did more changes than I thought…
So anyone who wants to generate the Doxygen docs of some FreeBSD kernel subsystems on his own, can do it now. Adding more subsystems is easy, just make a copy of one the the existing Doxyfile-* files – keep the same naming scheme – and change the contents. Everything else is handled automatically.
I also added a link to the FreeBSD wiki. It is not at a prominent place (near the end of the main page), but at least someone can find the link to the my FreeBSD-doxygen page there.
Wow, some of the TODO items in the last post are done:
- emu10k1 lower priority on attach (allows emu10kx to attach when loaded too)
- sade committed (and code improved)
And I did some more things:
- emu10kx fixes (submitted by Yuriy)
- enhancement of the bsd to linux errno mapping (submitted by “Intron”)
- added some more files to ObsoleteFiles.inc (submitted by kris@)
- had a look at linux_kdump and determined that we should update it with what we have in -current
There’s also a submission of support for Envy24HT chips from Konstantin (he also has a page with a lot of docs for envy* chips).