move the ID string from a pubdate element into a comment on the
grounds that this document doesn't change rapidly enough to require
that the ID string to actually be rendered in the output.
solves a pretty annoying problem, this release notes entry doesn't
describe what this fixes because I can't seem to figure out how to do
this without giving a lot of background.
net/cvsupd-bin. Also note CVSup update to fix S1G bug.
I'm breaking a self-imposed rule of not mentioning ports-collection
updates in release notes. I'm only doing this because CVSup is a
fairly essential part of the FreeBSD Project infrastructure. Save
for exceptions such as this, the release notes will continue to
document changes to the base system only.
Suggested by: mike
DESTDIR. This avoids redundant information in the path when DOCDIR
points to some directory that already implies (or specifies) a certain
language. This is the case with the web site, where the release notes
are already installed under a language-specific directory. This
behavior is not being made mandatory because it might still be useful
to install all the translations in one directory, such as during
testing, or in a hypothetical release notes archive. Furthermore, it
is not being made the default because that breaks consistency with
stuff under doc/.
Reviewed by: bmah
discussed on the arch@ mailinglist (after repo-copy).
sys.mk will .error if it finds /etc/defaults/make.conf but include
it anyways (this is the same behaviour as with the make.conf.local
removal).
/usr/share/examples/etc/make.conf has BDEFLAGS commented out now,
since it's only an example file.
Adjust all textes that talk about make.conf or defaults/make.conf to
match the new situation.
changes" section, but I'm not sure it's appropriate there. config(8)
is a userland utility, but this is actually a "kernel" feature. There
are release notes about config(8) in both sections, but "kernel" seems
more appropriate for this one.
1. Bring floppies.sgml section in-line into install.sgml, where it
makes more sense.
2. Slightly reorganize some sections of Installation section and
do some wordsmithing.
3. Update distribution layout to reflect RELNOTESng and new compat
distributions.
4. Update upgrade file list from 4-STABLE.
5. It's been a long time since 2.2.X; get rid of instructions dealing
with "new" handling of compatability slices and fix up other references
in the text.
6. Hunt down and kill emoticons with extreme prejudice. Try to
tone down the use of exclamation points.
7. Cross-reference new and improved Installation chapter in
Handbook.
8. Add a proper abstract for this document.
