NetBSD/external
2017-08-01 18:08:48 +00:00
..
apache2 Fix format strings to reflect exactly the types used. 2017-07-21 08:49:05 +00:00
atheros
broadcom/rpi-firmware/dist New firmware from 2017-01-12 05:20:07 +00:00
bsd Inline storage size in one place to avoid depending on DCE for removing 2017-08-01 18:08:48 +00:00
cddl Undo the previous 2017-06-05 21:19:32 +00:00
gpl2 Update the dtc version string to match the imported version and note that 2017-06-16 22:47:22 +00:00
gpl3 Apply upstream patch: 2017-07-28 22:24:27 +00:00
historical Use literal for formatting the examples 2017-05-23 14:11:08 +00:00
ibm-public Remove MKCRYPTO option. 2017-05-21 15:28:36 +00:00
intel-fw-eula
intel-fw-public iwm(4): update firmware to maintained core release. 2017-03-14 23:59:24 +00:00
lgpl3 Update supporting files for components which rely on autoconf to allow systems 2017-02-01 09:26:39 +00:00
mit Missed a MKCRYPTO spot. 2017-07-15 13:54:07 +00:00
public-domain Merge tzdata2017b 2017-03-21 19:24:22 +00:00
realtek Add firmaware for Realtek 8192ee/eu. 2016-10-12 06:49:40 +00:00
zlib/pigz
Makefile
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.