linux/meta-openembedded.git/meta-networking/recipes-connectivity/crda/crda_1.1.3.bb, branch sumo

crda: upgrade to 3.13

2015-02-23T18:21:07+00:00

CRDA has been relicensed under the copyleft-next license. Regulatory bins license remains ISC. There is an new internal library called libreg.so which was placed in the same directory of the regulatory bin. The call to make was adjusted accordingly. Remove version 1.1.3. Signed-off-by: Hugo Vasconcelos Saldanha Signed-off-by: Martin Jansa Signed-off-by: Joe MacDonald

crda: fix udev rule

2014-03-14T12:49:38+00:00

The SBINDIR variable in makefile's install rule needs to have a trailing slash so the path to the 'crda' binary in the udev rule is correct. Otherwise the udev rule has a wrong path: KERNEL=="regulatory*", ACTION=="change", SUBSYSTEM=="platform", RUN+="/usr/sbincrda" and at runtime udev complains: failed to execute '/usr/sbincrda' when a regulatory domain event is triggered. Signed-off-by: Javier Viguera Acked-by: Koen Kooi Signed-off-by: Joe MacDonald

recipes: convert remaining SUMMARY/DESCRIPTION cosmetic issues

2014-02-23T22:20:02+00:00

Changes: - rename SUMMARY with length > 80 to DESCRIPTION - rename DESCRIPTION with length < 80 to (non present tag) SUMMARY - drop final point character at the end of SUMMARY string - remove trailing whitespace of SUMMARY line Note: don't bump PR Signed-off-by: Matthieu Crapet Signed-off-by: Martin Jansa

crda: correct QA issues with sbindir

2013-11-06T15:36:48+00:00

regdbdump and crda are installed in /sbin/ and still link against stuff in /usr/lib, causing QA warnings / errors: WARNING: QA Issue: crda: /sbin/regdbdump, installed in the base_prefix, requires a shared library under exec_prefix (/usr): libgcrypt.so.11 => /usr/lib64/libgcrypt.so.11 (0x00000000dead1000) WARNING: QA Issue: crda: /sbin/regdbdump, installed in the base_prefix, requires a shared library under exec_prefix (/usr): libgpg-error.so.0 => /usr/lib64/libgpg-error.so.0 (0x00000000dead3000) WARNING: QA Issue: crda: /sbin/crda, installed in the base_prefix, requires a shared library under exec_prefix (/usr): libgcrypt.so.11 => /usr/lib64/libgcrypt.so.11 (0x00000000dead1000) WARNING: QA Issue: crda: /sbin/crda, installed in the base_prefix, requires a shared library under exec_prefix (/usr): libnl-genl-3.so.200 => /usr/lib64/libnl-genl-3.so.200 (0x00000000dead2000) WARNING: QA Issue: crda: /sbin/crda, installed in the base_prefix, requires a shared library under exec_prefix (/usr): libnl-3.so.200 => /usr/lib64/libnl-3.so.200 (0x00000000dead3000) WARNING: QA Issue: crda: /sbin/crda, installed in the base_prefix, requires a shared library under exec_prefix (/usr): libnl-nf-3.so.200 => /usr/lib64/libnl-nf-3.so.200 (0x00000000dead4000) WARNING: QA Issue: crda: /sbin/crda, installed in the base_prefix, requires a shared library under exec_prefix (/usr): libnl-route-3.so.200 => /usr/lib64/libnl-route-3.so.200 (0x00000000dead5000) WARNING: QA Issue: crda: /sbin/crda, installed in the base_prefix, requires a shared library under exec_prefix (/usr): libgpg-error.so.0 => /usr/lib64/libgpg-error.so.0 (0x00000000dead7000) relocate them to /usr/sbin to squelch the warning. Signed-off-by: Joe MacDonald

crda: Fix multilib SRC_URI reference

2013-05-10T13:45:45+00:00

Signed-off-by: Mark Hatle Signed-off-by: Joe MacDonald

recipes: Unify indentation

2013-04-15T14:23:17+00:00

* This change is only aesthetic (unlike indentation in Python tasks). * Some recipes were using tabs. * Some were using 8 spaces. * Some were using mix or different number of spaces. * Make them consistently use 4 spaces everywhere. * Yocto styleguide advises to use tabs (but the only reason to keep tabs is the need to update a lot of recipes). Lately this advice was also merged into the styleguide on the OE wiki. * Using 4 spaces in both types of tasks is better because it's less error prone when someone is not sure if e.g. do_generate_toolchain_file() is Python or shell task and also allows to highlight every tab used in .bb, .inc, .bbappend, .bbclass as potentially bad (shouldn't be used for indenting of multiline variable assignments and cannot be used for Python tasks). * Don't indent closing quote on multiline variables we're quite inconsistent wheater it's first character on line under opening quote or under first non-whitespace character in previous line. Signed-off-by: Martin Jansa Acked-by: Koen Kooi

crda: add 1.1.3

2013-04-02T12:53:13+00:00

Signed-off-by: Koen Kooi Signed-off-by: Joe MacDonald