NetBSD

History

atatat 7da213dc5f Only set DIST and .PATH if we are actually in the source tree. This solves the problem of trying to do a "make submit.cf" in the /usr/share/sendmail/cf directory where make gets confused by the out of date target in the .PATH, removes it (bad!) and then fails to make a new submit.cf file.		2003-03-31 20:57:30 +00:00
..
dist	bessel->Bessel (Igor Sobrado, PR misc/19700)	2003-03-31 02:43:38 +00:00
lib	Actually rerun mknative on these...	2003-03-20 14:47:36 +00:00
libexec	Correct spelling of "overridden". From PR 20718 by Igor Sobrado.	2003-03-15 19:22:16 +00:00
usr.bin	VAX, not Vax. Igor Sobrado in PR 19678.	2003-03-30 20:55:47 +00:00
usr.sbin	Only set DIST and .PATH if we are actually in the source tree. This	2003-03-31 20:57:30 +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.