Rant about Berke­ley­DB docs

I was build­ing Berke­ley­DB (4.7, yes I know, there are more re­cent ver­sions avail­able) on a Sol­ar­is ma­chine. First try was to un­pack, cd in­to the dir­ect­ory, run con­fig­ure. It failed, there is no con­fig­ure script. Bah. 🙁

Second try: search­ing for docs… found some… in HTML (the README refers to it and tells noth­ing else). This is a re­mote ma­chine, I do not want to use a HTML browser re­motely (I may not even have one in­stalled there…). Bah. 🙁

Ok, dist/​configure ex­ists, no spe­cial op­tions needed for my case, it seems.

There is even a Sol­ar­is spe­cif­ic HTML file, but from a quick glance at it with „less“, it looks like a FAQ.

Us­ab­il­ity from a com­mand line: zero.
Pos­sib­il­ity to com­pile from a GUI (unix): I doubt it.

What is wrong with plain text files? If I down­load the source and want to com­pile it (and for Sol­ar­is this is the nor­mal way of work­ing), why the hell do I need some GUI in­stead of get­ting a plain text file with the re­quired de­scrip­tion (which is not graph­ic­ally en­hanced in the HTML ver­sion either)? You can even gen­er­ate a plain text ver­sion of the docs auto­mat­ic­ally dur­ing the src-​packaging pro­cess.

Hey Or­acle, there is room for im­prove­ment here!

Leave a Reply

Your email address will not be published. Required fields are marked *