GayBSD documentation tree
57f6bf9869
1. Listing LIB_IMAGES as a dependency on certain targets, to ensure
that library images are pulled in correctly.
2. Create a new FORMAT, html.tar, to cater for the case where we might
be producing a single .html file, but we need to tar that up for
distribution and the tar file needs to include all the images.
3. Update the various install-* targets to include the images.
4. Update the package-* targets to include the images
While I'm here, pull out the .doc target. For some reason I thought our
tool chain could produce Microsoft Word .doc files. It can't.
|
||
|---|---|---|
| de_DE.ISO8859-1 | ||
| de_DE.ISO_8859-1 | ||
| en/handbook/contrib | ||
| en_US.ISO8859-1 | ||
| en_US.ISO_8859-1 | ||
| es_ES.ISO8859-1 | ||
| es_ES.ISO_8859-1 | ||
| fr_FR.ISO8859-1 | ||
| fr_FR.ISO_8859-1 | ||
| ja_JP.eucJP | ||
| nl_NL.ISO8859-1 | ||
| nl_NL.ISO_8859-1 | ||
| ru_RU.KOI8-R | ||
| share | ||
| zh/FAQ | ||
| zh_TW.Big5 | ||
| Makefile | ||
| README | ||
$FreeBSD$
If you plan on building a local copy of the FreeBSD documentation, or using
our toolchain in your own projects, please read
http://www.freebsd.org/tutorials/docproj-primer/
for information about the tools and formatting languages we use. Chapter
2 covers the software and related items you will need to install.