NetBSD

History

apb f90c5ef1d5 Use ${HOST_SH} instead of the host system's /bin/sh wherever possible: * Explicitly use $(SHELL) to run shell scripts. * Use SHELL = @SHELL@, not SHELL = /bin/sh. @SHELL@ will be substituted by associated configure scripts, and will actually refer to the environment variable ${CONFIG_SHELL}.		2006-09-29 20:08:36 +00:00
..
dist	Use ${HOST_SH} instead of the host system's /bin/sh wherever possible:	2006-09-29 20:08:36 +00:00
lib	Bootstrap for ia64	2006-09-14 23:48:28 +00:00
libexec	Fix uninitialized variable.	2006-05-13 23:49:02 +00:00
usr.bin	make this build with ro srcdir: ignore yacc-generated files in dist	2006-09-27 18:37:41 +00:00
usr.sbin	Install aliases(5) from postfix, since the sendmail one is gone,	2006-09-19 20:10:22 +00:00
Makefile
README

README

$NetBSD: README,v 1.5 2003/12/04 23:32:37 keihan 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.