aboutsummaryrefslogtreecommitdiffstats
path: root/meta-oe/recipes-support/xchat
AgeCommit message (Collapse)Author
2017-04-05recipes: add removal date to PNBLACKLIST messagesMartin Jansa
* based on discussion in pndeprecated thread: https://patchwork.openembedded.org/patch/137573/ update the messages to warn possible users that the recipe will be removed before the end of the next development cycle (before Yocto 2.4 is released). * updated with: sed -i 's/^\(PNBLACKLIST.*".*\)"/\1 - the recipe will be removed on 2017-09-01 unless the issue is fixed"/g' `git grep PNBLACKLIST | sed 's/:.*//g' | sort -u | xargs` * then noticed couple recipes being blacklisted only based on DISTRO_FEATURES, so removed those: meta-networking/recipes-support/lksctp-tools/lksctp-tools_1.0.17.bb meta-oe/recipes-connectivity/bluez/bluez-hcidump_2.5.bb meta-oe/recipes-connectivity/bluez/bluez4_4.101.bb meta-oe/recipes-connectivity/bluez/gst-plugin-bluetooth_4.101.bb meta-oe/recipes-navigation/foxtrotgps/foxtrotgps_1.1.1.bb meta-oe/recipes-navigation/gypsy/gypsy.inc meta-oe/recipes-navigation/navit/navit.inc meta-oe/recipes-support/opensync/libsyncml_0.5.4.bb * if it isn't fixed by this date, it's fair game to be removed whenever someone gets around to i Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2017-02-13recipes: blacklist recipes depending on blacklisted recipesMartin Jansa
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2014-09-26xchat: update recipe with build/configure fixesstephen.arnold42
Update recipe with build/configure fixes (rework autotools config, add patch for separate build dir, add patch for automake foreign, add PACKAGECONFIG option for python interface, move dbus to RDEPEND, as dbus-glib header is required for build; the last one is a workaround for the QA depend warning on more than one dep in PKGCONF). Upstream-Status: Inappropriate (no more upstream) Signed-off-by: S. Lockwood-Childs <sjl@vctlabs.com> Signed-off-by: Steve Arnold <stephen.arnold42@gmail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2014-06-21xchat: Blacklist because of broken with B!=SMartin Jansa
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.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-09-17xchat: Add PACKAGECONFIG for dbus and opensslMartin Jansa
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>
2013-02-01xchat: add libsexy to DEPENDSMartin Jansa
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2012-07-31fbreader, fltk, gpm, iksemel, joe, links, ode, openldap, opensync, xchat: ↵Martin Jansa
import from meta-smartphone Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>