NetBSD/external
mrg ba39e0d4ed revert previous; it was already done in the previous previous.
while here, make freetype-config depend upon Makefile, so it
will be rebuilt for update builds properly.
2013-06-08 00:37:33 +00:00
..
apache2
atheros build glue 2013-03-30 02:47:56 +00:00
broadcom/rpi-firmware/dist New firmware from today 2013/03/09 2013-03-09 10:58:44 +00:00
bsd Sync 2013-06-04 09:40:12 +00:00
cddl stub out for now 2013-04-14 16:52:47 +00:00
gpl2 When checking for membership in the system group file don't forget to check 2013-05-09 15:25:44 +00:00
gpl3 and m68000 == m68k 2013-05-24 16:37:32 +00:00
historical PR/47553: Aleksev Cheusov: awk segfault: NULL dereference. 2013-02-11 00:32:07 +00:00
ibm-public Comment out "inet_protocols = ipv4" line which came from up-stream. 2013-01-06 13:58:24 +00:00
intel-fw-eula
intel-fw-public
lgpl2/mpc
lgpl3 Add earmhfeb libgmp files. 2013-05-08 05:42:17 +00:00
mit revert previous; it was already done in the previous previous. 2013-06-08 00:37:33 +00:00
public-domain Backout libm dependency here as well (assuming it was meant for the 2013-02-15 07:59:36 +00:00
realtek
zlib/pigz
Makefile
README

README

$NetBSD: README,v 1.15 2012/06/14 04:14:36 riz Exp $

Organization of Sources:

This directory hierarchy is using an organization that separates
source for programs that we have obtained from external third
parties (where NetBSD is not the primary maintainer) from the
system source.

The hierarchy is grouped by license, and then package per license,
and is organized as follows:

	external/

	    Makefile
			Descend into the license sub-directories.

	    <license>/
			Per-license sub-directories.

		Makefile
			Descend into the package sub-directories.

		<package>/
			Per-package sub-directories.

		    Makefile
			Build the package.
			
		    dist/
			The third-party source for a given package.

		    bin/
		    lib/
		    sbin/
			BSD makefiles "reach over" from these into
			"../dist/".

This arrangement allows for packages to be easily disabled or
excised as necessary, either on a per-license or per-package basis.

The licenses currently used are:

	apache2		Apache 2.0 license.
			http://www.opensource.org/licenses/apache2.0.php

	atheros		Atheros License.

	bsd		BSD (or equivalent) licensed software, possibly with
			the "advertising clause".
			http://www.opensource.org/licenses/bsd-license.php

	cddl		Common Development and Distribution License (the sun
			license which is based on the Mozilla Public License
			version 1.1).
			http://www.opensource.org/licenses/cddl1.php

	gpl2		GNU Public License, version 2 (or earlier).
			http://www.opensource.org/licenses/gpl-2.0.php

	gpl3		GNU Public License, version 3.
			http://www.opensource.org/licenses/gpl-3.0.html

	historical	Lucent's old license:
			http://www.opensource.org/licenses/historical.php
			
	ibm-public	IBM's public license:
			http://www.opensource.org/licenses/ibmpl.php

	intel-fw-eula	Intel firmware license with redistribution
			restricted to OEM.

	intel-fw-public	Intel firmware license permitting redistribution with
			terms similar to BSD licensed software.

	intel-public	Intel license permitting redistribution with
			terms similar to BSD licensed software.

	mit		MIT (X11) style license.
			http://www.opensource.org/licenses/mit-license.php

	public-domain	Non-license for code that has been explicitly put
			into the Public Domain.

	realtek		RealTek license.

	zlib		Zlib (BSD-like) license.
			http://www.zlib.net/zlib_license.html

If a package has components covered by different licenses
(for example, GPL2 and the LGPL), use the <license> subdirectory
for the more restrictive license.

If a package allows the choice of a license to use, we'll
generally use the less restrictive license.

If in doubt about where a package should be located, please
contact <core@NetBSD.org> for advice.


Migration Strategy:


Eventually src/dist (and associated framework in other base source
directories) and src/gnu will be migrated to this hierarchy.


Maintenance Strategy:

The sources under src/external/<license>/<package>/dist/ are
generally a combination of a published distribution plus changes
that we submit to the maintainers and that are not yet published
by them.

Make sure all changes made to the external sources are submitted
to the appropriate maintainer, but only after coordinating with
the NetBSD maintainers.