aboutsummaryrefslogtreecommitdiffstats
path: root/meta-networking/recipes-daemons/pure-ftpd/pure-ftpd_1.0.36.bb
AgeCommit message (Collapse)Author
2015-06-05meta-networking: standardize SECTION valuesJoe MacDonald
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>
2014-02-23recipes: convert remaining SUMMARY/DESCRIPTION cosmetic issuesMatthieu CRAPET
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 <Matthieu.Crapet@ingenico.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2013-11-01recipes: Remove PR = r0 from all recipesMartin Jansa
* Remove all PR = "r0" from all .bb files in meta-oe repo. This was done with the command sed -e '/^PR.*=.*r0\"/d' meta*/recipes*/*/*.bb -i * We've switching to the PR server, PR bumps are no longer needed and this saves people either accidentally bumping them or forgetting to remove the lines (r0 is the default anyway). Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2013-04-15recipes: Unify indentationMartin Jansa
* 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>
2012-12-07pure-ftpd: add new recipe for 1.0.36Paul Eggleton
Based on a patch by Yauhen Kharuzhy <yauhen.kharuzhy@promwad.com> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>