Files
meta-openembedded/meta-networking
Joe Slater 37edcea5b7 xl2tpd: modify recipes to avoid forced internet access
We should always specify a commit id for git SRCREV or
we will try to access the upstream repo when fetching.

In addition, if our PV is just "git" we will access upstream
when doing archiver functions, so we should specify PV for
xyz_git.bb recipes.

Signed-off-by: Joe Slater <jslater@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>
2016-01-20 21:41:46 -05:00
..
2014-11-24 14:12:02 -05:00
2015-02-23 13:21:07 -05:00
2016-01-20 21:41:44 -05:00
2016-01-20 21:41:45 -05:00
2012-08-27 14:16:45 +02: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.