NetBSD/gnu
matt 046e9000ba Make etime_.* and dtime_.* explicitly depend on the libU77 version.
Include *.d so that when make depend emit the dependencies, it picks up
the right file and so that the right file is used when making the objects.
2003-10-10 23:34:20 +00:00
..
dist Add rules to prevent c-parse.c and objc-parse.c from being rebuilt if the 2003-10-10 15:25:17 +00:00
lib Make etime_.* and dtime_.* explicitly depend on the libU77 version. 2003-10-10 23:34:20 +00:00
libexec possible scanf overrun 2003-05-17 15:05:19 +00:00
usr.bin Turn on HAVE_GAS_HIDDEN. 2003-10-07 02:19:18 +00:00
usr.sbin Don't install libsm. Instead, pull a couple of things over into 2003-09-22 12:54:46 +00:00
Makefile Make "make includes" descend into the sendmail tree. 2003-07-04 04:53:50 +00:00
README Remove completely outdated maintenance history, and add proper NetBSD RCS tag. 2002-09-22 09:47:56 +00:00

$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.