NetBSD

History

dan 7e85dcc65c switch pickup and qmgr to unix sockets instead of fifos. This helps avoid postfix waking up an idle disk with mtime updates for fifos. Evidently only fifos worked for these two in earlier postfix versions, but now it works fine in my testing, and it also makes the config consistent for all postfix services. Thanks to Charles Hannum.		2004-05-20 22:06:52 +00:00
..
dist	switch pickup and qmgr to unix sockets instead of fifos.	2004-05-20 22:06:52 +00:00
lib	(pretend to) run mknative for hppa and pick up the -DNETBSD=1 addition	2004-04-30 08:15:47 +00:00
libexec	Replace the statfs() family of system calls with statvfs().	2004-04-21 01:05:31 +00:00
usr.bin	Prefer the new -std=c89 over -ansi.	2004-05-20 18:53:08 +00:00
usr.sbin	Consistently use CONFIGFILES & CONFIGLINKS (which enable the 'configinstall'	2004-05-16 09:53:09 +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.