linux/meta-openembedded.git/meta-oe/recipes-support/mime-support, branch styhead-next

Convert to new override syntax

2021-08-03T17:21:25+00:00

This is the result of automated script (0.9.1) conversion: oe-core/scripts/contrib/convert-overrides.py . converting the metadata to use ":" as the override character instead of "_". Signed-off-by: Martin Jansa

mime-support: upgrade 3.48 -> 3.62

2021-05-28T13:55:33+00:00

* Many changes since 2009 (!!!) - most notable: CVE-2014-7209: run-mailcap shellcommand injection. * They added Bellcore license for mailcap.man * There is a later version 3.66 available but tarball is almost empty because with 3.65 they splitted mime-support into several packages Signed-off-by: Andreas Müller Signed-off-by: Khem Raj

mime-support: Use update-alternatives

2020-08-31T15:30:19+00:00

mime.types is also provided by mailcap so use update-alternatives to install is policy when both are added into image Signed-off-by: Khem Raj

mime-support: fix PN -> BPN for multilib

2015-05-13T12:32:01+00:00

Signed-off-by: Yi Zhao Signed-off-by: Martin Jansa

mime-support: add perl to RDEPENDS

2014-10-16T05:01:00+00:00

most executables are perl scripts. fix | mime-support-3.48: mime-support requires /usr/bin/perl, but no providers in its RDEPENDS [file-rdeps] Signed-off-by: Andreas Müller

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

mime-support: Drop allarch

2013-12-05T18:46:40+00:00

* depends on TUNE_PKGARCH 'file' Signed-off-by: Martin Jansa

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

mime-support: Update to version 3.48

2012-04-18T17:19:24+00:00

Signed-off-by: Luca Vaudano Signed-off-by: Martin Jansa Signed-off-by: Koen Kooi

recipes: use allarch.bbclass instead just PACKAGE_ARCH = all

2011-06-02T08:04:54+00:00

* otherwise such recipes are rebuilt or reused from sstate after every MACHINE change, because of different checksums see [YOCTO #1075] Signed-off-by: Martin Jansa