NetBSD

History

lukem 8c51a2ac71 When creating a "stamp" file with cp(1), explicitly provide the target file name rather than relying upon "$@", since the latter might be the path to an older version of the "stamp" file located in (possibly read-only) source. Fixes an annoying-to-debug build problem I hit in tools/texinfo...		2003-01-19 04:57:20 +00:00
..
dist	When creating a "stamp" file with cp(1), explicitly provide the target	2003-01-19 04:57:20 +00:00
lib	Remove more old toolchain bits.	2002-09-17 23:24:52 +00:00
libexec	writable, not writeable.	2003-01-06 20:30:28 +00:00
usr.bin	merge nathanw_sa	2003-01-18 21:36:47 +00:00
usr.sbin	allow NO_SENDMAIL to equal "no"	2003-01-09 16:57:45 +00:00
Makefile	Use @true instead of @${TRUE} in includes-foo targets, since there is no	2001-10-12 21:05:08 +00:00
README	Remove completely outdated maintenance history, and add proper NetBSD RCS tag.	2002-09-22 09:47:56 +00:00

README

$NetBSD: README,v 1.4 2002/09/22 09:47:56 wiz Exp $

Organization of Sources:

This directory hierarchy is using a new organization that
separates the GNU sources from the BSD-style infrastructure
used to build the GNU sources.  The GNU sources are kept in
the standard GNU source tree layout under:

	dist/*

The build infrastructure uses the normal BSD way under:

	lib/*
	usr.bin/*

The makefiles in the above hierarchy will "reach over" into
the GNU sources (src/gnu/dist) for everything they need.


Maintenance Strategy:

The sources under src/gnu/dist are generally a combination of
some published distribution plus changes that we submit to the
maintainers and that are not yet published by them.  There are
a few files that are never expected to be submitted to the FSF,
(i.e. BSD-style makefiles and such) and those generally should
stay in src/gnu/lib or src/gnu/usr.bin (the BSD build areas).

Make sure all changes made to the GNU sources are submitted to
the appropriate maintainer, but only after coordinating with the
NetBSD maintainers by sending your proposed submission to the
<tech-toolchain@netbsd.org> mailing list.  Only send the changes
to the third-party maintainers after consensus has been reached.