before parsing the command line.
Move code to build include and libraries in a separate function,
so we can use the verbose flag for that.
Chang ownership of some directories so more of the build process
(namely, builds of include and libs) can be run without root
permission (we still depend on root permission to mount a memory
filesystem).
come from the installation document (of the release documentation)
not the readme. The installation document is the one that has the
content of the old FLOPPIES.TXT.
Pointy hat to: bmah
MFCs noted: cat(1) UNIX-domain sockets, dirpref.
While I'm here, group CVS-related items together in their own section
under userland contributed software.
as well. This works by selecting "md" or "vn" depending on "uname -r"
output, so we can use the same script on -CURRENT and -STABLE.
Also included minor bugfixes and code cleanup.
Testers welcome, as this code has only been tested on -STABLE
(and for this reason I am doing an immediate MFC).
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
so as to make the "picobsd" script less version-specific.
Improve handling of cross-builds (which requires creation of
includes and libraries for the new source tree).
The "picobsd" script will not probably work on -current because it still
uses 'vn' instead of 'md', but i am commiting it anyways to keep it
in sync with the version in -stable.
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
I guess I pooched the permissions on the scripts before committing them
since they're not executable and now it's too late to change (I think -
I suppose you could chmod the ,v files and it might inheirit but I don't
feel like asking the repomeisters to try that).
Noticed by: Dirk Froemberg <dirk@freebsd.org>
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.
- build_x.sh now does all the steps to build an X dist rather than being
a child script of package_x_dists.sh
- Update the usage information to list the ports you need to install
before running this script as well as needing to set CVSROOT.
- Make sure CVSROOT is set. If not, exit with an error.
- We now take two parameters: a work directory and an output directory.
The work directory is used as scratch space. All of the bindist will
end up in the output directory.
- Only apply XF86.patch to the checked out XFree86 port if it exists.
- Use XFree86's build-bindist tool to package up the dists using their
distfiles rather than using our own packing lists that have to be
manually updated each time the port changes.
Example usage:
env CVSROOT=/home/ncvs ./build_x.sh /usr/xtmp /usr/x11dists
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.
