path: root/meta-networking/recipes-support/ndisc6
Commit message (Collapse)AuthorAgeFilesLines
* ndisc6: specify target location of perlJoe Slater2017-08-311-0/+5
| | | | | | | configure finds the host perl, so we do not let it look by setting PERL in the environment. Signed-off-by: Joe Slater <jslater@windriver.com>
* ndisc6: Upgrade to 1.0.3Khem Raj2017-08-311-2/+2
| | | | | Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* meta-networking: standardize SECTION valuesJoe MacDonald2015-06-051-2/+1
| | | | | | | SECTION has been used inconsistently throughout the recipes in this layer. Convert them to all use the same convention. Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>
* ndisc6: add perl to RDEPENDS_ndisc6-miscRobert Yang2014-09-261-0/+1
| | | | | | | Perl: ndisc6-misc/usr/bin/dnssort:#! /usr/bin/perl Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
* ndisc6: allow the package can be emptyKai Kang2014-04-241-0/+2
| | | | | | | | | | | | | FILES_${PN} is set to null in original .bb file, this would cause ndisc6 main package is missing, then one build error will happen: ERROR: ndisc6 not found in the base feeds (qemux86 i586 x86 noarch any all). To fix this, need to set ALLOW_EMPTY_${PN} = "1". Signed-off-by: Xudong.zhu <xudong.zhu@windriver.com> Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Joe MacDonald <joe@deserted.net>
* ndisc6: chmod in do_install and remove unnecessary pkg_postinstChen Qi2013-10-311-10/+4
| | | | | | | | We can use chmod to set the SUID bit for applications in the do_install task. If we do so, the pkg_postinsts are no longer needed. Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Joe MacDonald <joe@deserted.net>
* recipes: Unify indentationMartin Jansa2013-04-151-18/+18
| | | | | | | | | | | | | | | | | | | | | | | | | * 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 <Martin.Jansa@gmail.com> Acked-by: Koen Kooi <koen@dominion.thruhere.net>
* ndisc6: Forward port recipe from OE classicKhem Raj2013-01-081-0/+62
Signed-off-by: Khem Raj <raj.khem@gmail.com>