NetBSD

History

jwise 48f45412af As discussed on tech-toolchain@netbsd.org, make cpp refuse to attempt to parse a #include'd file which does not pass S_ISREG() if the environment variable CPP_RESTRICTED is set. This is primarily intended for use by programs such as calendar(1) which use cpp to parse untrusted user files -- without this change (and the corresponding change to calendar(1)), any user can cause a denial-of-service for the daily calendar -a run by #include'ing a named pipe. Many thanks to christos@netbsd for his help in polishing this.		2004-11-30 01:51:13 +00:00
..
dist	As discussed on tech-toolchain@netbsd.org, make cpp refuse to attempt to	2004-11-30 01:51:13 +00:00
lib	Switch to using GCC's supplied crtbegin / crtend files.	2004-08-28 00:18:38 +00:00
libexec	Add (unsigned char) cast to ctype functions	2004-11-05 19:56:34 +00:00
usr.bin	Initial import of iyonix port.	2004-10-13 23:28:34 +00:00
usr.sbin	add postconf.5.html OVERVIEW.html	2004-09-07 23:56:08 +00:00
Makefile	Install the MMX/SSE/Altivec include files that gcc provides.	2003-12-05 18:56:11 +00:00
README	netbsd.org -> NetBSD.org	2003-12-04 23:32:37 +00:00

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.