Mikko Rapeli d12ea80ef5 mdns: add BSD-3-Clause to LICENSE
The LICENSE file in source tree says:

The majority of the source code in the mDNSResponder project is licensed
under the terms of the Apache License, Version 2.0, available from:
   <http://www.apache.org/licenses/LICENSE-2.0>

To accommodate license compatibility with the widest possible range
of client code licenses, the shared library code, which is linked
at runtime into the same address space as the client using it, is
licensed under the terms of the "Three-Clause BSD License".

The Linux Name Service Switch code, contributed by National ICT
Australia Ltd (NICTA) is licensed under the terms of the NICTA Public
Software Licence (which is substantially similar to the "Three-Clause
BSD License", with some additional language pertaining to Australian law).

Signed-off-by: Mikko Rapeli <mikko.rapeli@bmw.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2020-09-08 11:53:53 -07:00
..
2019-07-10 09:24:32 -07:00
2015-02-23 13:21:07 -05:00
2020-09-03 07:54:13 -07:00
2020-09-03 07:54:13 -07:00
2012-08-27 14:16:45 +02:00
2018-10-02 17:53:46 -07:00

meta-networking
===============

This layer is intended to be a central point for networking-related
packages and configuration.  It should be useful directly on top of
oe-core and compliments meta-openembedded.  It should be primarily useful
to the following groups:

      - Anyone building a small networking device (eg. a home router /
        bridge / switch).

      - Anyone wanting to add network services to their device (eg.
        anything that might benefit from a small ftp/tftp server)

Dependencies
------------

This layer depends on:

URI: git://github.com/openembedded/openembedded-core.git
branch: master
revision: HEAD

For some recipes, the meta-oe layer is required:

URI: git://github.com/openembedded/meta-openembedded.git
subdirectory: meta-oe
branch: master
revision: HEAD

URI: git://github.com/openembedded/meta-openembedded.git
subdirectory: meta-python
branch: master
revision: HEAD

Maintenance
-----------

Please see the MAINTAINERS file for information on contacting the
maintainers of this layer, as well as instructions for submitting patches.