* 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>
* "vala-dbus-binding-tool_version" string ends as the version and e.g. libfso-glib doesn't like it at all
| configure: error: Package requirements (vala-dbus-binding-tool-1.0 >= 0.4.0) were not met:
| Requested 'vala-dbus-binding-tool-1.0 >= 0.4.0' but version of Vala-DBus-Binding-Tool is vala-dbus-binding-tool_version
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* new version of vala-dbus-binding-tool was released with 0.4.0 version
but unfortunately there already was 0.4.0 and 0.4.1 version, see
comment in git recipe for more details
* be aware that it's actually newer than 0.4.1 used before
and it's compatible with gee-0.8 which is newer than gee-1.0
and yes I know how incorrect it sounds, but it's truth
* remove negative preference from git recipe so it's used by default
and most people wont notice the mess with 0.4.0 archives
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
It's not necessary to specify the protocol parameter when it's the
default protocol for the fetcher, e.g. the default protocol for
git fetcher it git, "protocol=git" isn't needed.
Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Martin Jansa
Jackie Huang