Software - qd-tools - Documentation

  _     _                  __  __ _           _          _
 | |   (_)_ __  _   ___  _|  \/  (_)_ __   __| | ___  __| |
 | |   | | '_ \| | | \ \/ / |\/| | | '_ \ / _` |/ _ \/ _` |
 | |___| | | | | |_| |>  <| |  | | | | | | (_| |  __/ (_| |
 |_____|_|_| |_|\__,_/_/\_\_|  |_|_|_| |_|\__,_|\___|\__,_|

Software

qd-tools

| General | Documentation | Credit History |

README
CREDITS
LICENSE
ChangeLog

compilation-information.txt
manpage-qdinfo.dat.txt
qd-output-example-linux.txt
qd-output-example-osx-from-linux.txt
qd-output-example-osx.txt
qd-xml-output-example-linux.txt
qd-xml-output.dtd
qd.c-defines.txt
update-qd.log
update-qd.txt
xml-ouput.txt

qd / queue.dat documentation
Using qd HOWTO
Dick Howells F@H Tools Page

$ cat update-qd.txt

update-qd.pl
============

Use this tool to update qd.c and/or qdinfo.dat with the data from 
Stanfords psummary.html file.

If the project/credit data in qdinfo.dat is not in sync with that in qd.c, 
the inconsistency will get worse as the data in psummary.html is only checked
against that of qdinfo.dat.

In general it does the following:
- Download psummary.html from Stanfords webserver
- Read the project/credit information from qdinfo.dat
- Compare the project/credit info from psummary.html to that of qdinfo.dat
- Generate a new qdinfo.dat with the original qdinfo.dat info and the updated 
  info from psummary.html
- Read the source of qd.c and grab its project/credit data
- Update the project/credit data in qd.c with that from psummary.html
- Save the updated qd.c and compile if requested with -c flag.


Dependencies
------------
It needs to be run on a UNIX machine or any other OS which uses / as a
directory separator and 1 January 1970 00:00:00 UTC as its epoch.

The script requires some Perl modules to work:
- Date::Calc
- LWP::UserAgent
- Getopt::Mixed

Fortune:

Q:      How many hardware engineers does it take to change a light bulb?
A:      None.  We'll fix it in software.

Q:      How many system programmers does it take to change a light bulb?
A:      None.  The application can work around it.

Q:      How many software engineers does it take to change a light bulb?
A:      None.  We'll document it in the manual.

Q:      How many tech writers does it take to change a light bulb?
A:      None.  The user can figure it out.