NetBSD

History

martin 14cde9f60d Add a few dependencies to make sure libtar/fnmatch.h is generated before anything includes <fnmatch.h>. Using our native /usr/include/fnmatch.h is no good idea, they are incompatible. XXX - why is tar using it's own implementation? I'm not sure this is the right way to handle the problem, but it made a "make cleandir && make" here possible again.		2002-10-13 18:41:48 +00:00
..
dist	If we're going to rely on a pre-generated getdate.c, we might as well rely	2002-10-11 08:58:44 +00:00
lib	Remove more old toolchain bits.	2002-09-17 23:24:52 +00:00
libexec	- use NETBSDSRCDIR as appropriate	2002-09-19 03:09:31 +00:00
usr.bin	Add a few dependencies to make sure libtar/fnmatch.h is generated before	2002-10-13 18:41:48 +00:00
usr.sbin	move mbone tools out of basesrc, as they use part of mrouted	2002-10-01 03:50:07 +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.