much of that these days. Create a new listing under `standards'; anyone
else who is involved in standardization activities (e.g., the Austin Group)
is welcome to add his name here.
Approved by: nik (ages ago)
Obtained from: other freebsd.dsl files in the doc tree
The commit for the Russian documentation was incomplete. The result was
the path changing, but the "SYSTEM" -> "PUBLIC" keyword did not. This fix
changes only this. At this point I beleive 'make release' will once again
function for 4.1.1-STABLE.
a) Because it's a cool piece of documentation
b) It's a real world example of using images in the documentation.
It's not turned on in the upper level Makefile yet, as I expect the
specifics of the toolchain to change over the next week or so as people
play around with this, and I don't want to the doc build mirrors to have
to suddenly update the ports they have installed. Once this has stabilised
it can be turned on.
For producing text-only docs, we need to have a second HTML target.
The PS and PDF targets (which depended on a .tex file) have been split
out so that they each depend on their own .tex-${format} file, to get
the image formats correct.
. FreeBSD is based on 4.4BSD-Lite2, not Lite
. fix latest release link: 4.1 -> 4.1.1
. mention 3.5.1R and 4.1.1R in FreeBSD releases tree.
. note that now we have more than 200 committers
. bump referenced releases numbers
. fix cut'n'paste error (USB mouse -> USB keyboard)
. few whitespace fixes
. mention IA64 port
(1) Describe the change in ports skeleton layout. I think I caught
everything, but please let me know if I missed something.
(2) Explicitly allow using things other than the "split" sequence (aa,
ab, ac...) in patchfile names, in particular those that represent
the names of the files being patched.
(3) Add a little note recommending the use of DISTFILES over
DISTNAME/WRKSRC/EXTRACT_SUFX when the source extracts into
${WRKDIR}/${PORTNAME}-${PORTVERSION} but the archive filename is
not ${PORTNAME}-${PORTVERSION}.tar.gz.
(4) There is error checking in category names now.
(5) There are more MASTER_SITE_* variables now, so just list a couple
and refer the readers to bsd.sites.mk.
(6) Explain EXTRACT_PATCHES. In particular, note that you shouldn't
copy patches into ${PATCHDIR}.
(7) Mention that pkg-install is called with sh.
(8) The first letter of the package name should be lowercase. (We'll
rename existing ports soon.)
While I'm here, fix a couple of minor indenting problems in the
paragraphs I was editing. It seems emacs some times messes up
auto-indentation, causing stuff like
===
<para>This is <emphasis>not</emphasis> a manual or an in-depth
description on how to use or compile the port! <emphasis>Please
be careful if you are copying from the
===
(the "be careful" should be in the same level as "description")
Also, convert a couple of "Note that" to real <note>'s.
