meta-openembedded/meta-multimedia
Jackie Huang 0487ed7f1d recipes: fix invalid license file
Use '${COMMON_LICENSE_DIR}/MIT' for MIT License to fix the warning:

| WARNING: packagegroup-xfce-base-1.0-r5 do_populate_lic:
  ${COREBASE}/LICENSE is not a valid license file, please use
  '${COMMON_LICENSE_DIR}/MIT' for a MIT License file in LIC_FILES_CHKSUM.
  This will become an error in the future

Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2017-09-18 10:18:12 +02:00
..
classes juce: Updated JUCE to 5.0.1 2017-05-23 15:49:34 +02:00
conf layer.conf: add LAYERVERSION and LAYERDEPENDS 2016-10-03 19:19:55 +02:00
recipes-connectivity libupnp: Add recipe for version 1.8.2 2017-09-18 10:18:11 +02:00
recipes-dvb/oscam recipes: remove blacklisted recipes 2017-08-31 10:18:33 +02:00
recipes-mediacenter/kodi recipes: remove blacklisted recipes 2017-08-31 10:18:33 +02:00
recipes-mkv recipes: remove blacklisted recipes 2017-08-31 10:18:33 +02:00
recipes-multimedia recipes: fix invalid license file 2017-09-18 10:18:12 +02:00
recipes-support crossguid: Add recipe 2017-07-14 23:44:30 +02:00
COPYING.MIT meta-multimedia: initial add 2012-02-24 13:53:17 +01:00
README README: show github mirror URL in layer dependencies 2013-05-03 13:32:03 +02:00

This layer depends on:

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

URI: git://github.com/openembedded/meta-oe.git
layers: meta-oe, meta-ruby
branch: master
revision: HEAD

Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-multimedia]' in the subject'

When sending single patches, please use something like:
'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-multimedia][PATCH

You are encouraged to fork the mirror on github https://github.com/openembedded/meta-oe/ to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like gitorious, repo.or.cz or self hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend github because it is free, easy to use, has been proven to be reliable and has a really good web GUI.

Main layer maintainers: Koen Kooi <koen@dominion.thruhere.net>
                        Martin Jansa <martin.jansa@gmail.com>