<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-openembedded.git/meta-gnome/recipes-gnome/pimlico/contacts_git.bb, branch hardknott</title>
<subtitle>Mirror of git.openembedded.org/meta-openembedded</subtitle>
<id>https://git.enea.com/cgit/linux/meta-openembedded.git/atom?h=hardknott</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-openembedded.git/atom?h=hardknott'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/'/>
<updated>2017-08-31T08:18:33+00:00</updated>
<entry>
<title>recipes: remove blacklisted recipes</title>
<updated>2017-08-31T08:18:33+00:00</updated>
<author>
<name>Martin Jansa</name>
<email>Martin.Jansa@gmail.com</email>
</author>
<published>2017-04-27T09:04:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=ec9e5ed06256ad92c818474cdb490dc0d3a0d0a3'/>
<id>urn:sha1:ec9e5ed06256ad92c818474cdb490dc0d3a0d0a3</id>
<content type='text'>
* as PNBLACKLIST message says, these recipes are blacklisted for long
  time and nobody showed any interest to fix them
* remove all unused .patch and .inc files as well

Signed-off-by: Martin Jansa &lt;Martin.Jansa@gmail.com&gt;
</content>
</entry>
<entry>
<title>recipes: add removal date to PNBLACKLIST messages</title>
<updated>2017-04-05T17:36:45+00:00</updated>
<author>
<name>Martin Jansa</name>
<email>Martin.Jansa@gmail.com</email>
</author>
<published>2017-04-05T17:35:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=cdb428e7c49899675ee7b7a43f6cecdb5b4c2546'/>
<id>urn:sha1:cdb428e7c49899675ee7b7a43f6cecdb5b4c2546</id>
<content type='text'>
* 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 &lt;Martin.Jansa@gmail.com&gt;
</content>
</entry>
<entry>
<title>smbnetfs gnome-disk-utility contacts kexecboot initramfs-kexecboot-klibc-image system-config-keyboard system-setup-keyboard geany geany-plugins efivar efibootmgr gimp system-config-keyboard tumbler: Blacklist</title>
<updated>2017-02-13T19:34:21+00:00</updated>
<author>
<name>Martin Jansa</name>
<email>Martin.Jansa@gmail.com</email>
</author>
<published>2017-02-13T17:51:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=044e5189549de11b2a94efd29a6009a76162b8f1'/>
<id>urn:sha1:044e5189549de11b2a94efd29a6009a76162b8f1</id>
<content type='text'>
* fails repeatedly as reported in:
  http://lists.openembedded.org/pipermail/openembedded-devel/2017-February/111112.html
  http://lists.openembedded.org/pipermail/openembedded-devel/2017-February/111173.html
  http://lists.openembedded.org/pipermail/openembedded-devel/2017-February/111180.html

Signed-off-by: Martin Jansa &lt;Martin.Jansa@gmail.com&gt;
</content>
</entry>
<entry>
<title>recipes: blacklist recipes depending on blacklisted recipes</title>
<updated>2017-02-13T17:44:35+00:00</updated>
<author>
<name>Martin Jansa</name>
<email>Martin.Jansa@gmail.com</email>
</author>
<published>2017-02-11T16:40:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=00ba7da845b96a15b42550d15a343f7bc36392f8'/>
<id>urn:sha1:00ba7da845b96a15b42550d15a343f7bc36392f8</id>
<content type='text'>
Signed-off-by: Martin Jansa &lt;Martin.Jansa@gmail.com&gt;
</content>
</entry>
<entry>
<title>remove the unnecessary protocol parameters</title>
<updated>2013-09-03T14:59:13+00:00</updated>
<author>
<name>Jackie Huang</name>
<email>jackie.huang@windriver.com</email>
</author>
<published>2013-09-02T02:54:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=b79176adb306d6802d1219dfadfa7ffe080efb22'/>
<id>urn:sha1:b79176adb306d6802d1219dfadfa7ffe080efb22</id>
<content type='text'>
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 &lt;jackie.huang@windriver.com&gt;
Signed-off-by: Martin Jansa &lt;Martin.Jansa@gmail.com&gt;
</content>
</entry>
<entry>
<title>recipes: Unify indentation</title>
<updated>2013-04-15T14:23:17+00:00</updated>
<author>
<name>Martin Jansa</name>
<email>Martin.Jansa@gmail.com</email>
</author>
<published>2013-04-13T20:49:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=a45830a39bb47a9eab27980d52966226c9504ea4'/>
<id>urn:sha1:a45830a39bb47a9eab27980d52966226c9504ea4</id>
<content type='text'>
* 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 &lt;Martin.Jansa@gmail.com&gt;
Acked-by: Koen Kooi &lt;koen@dominion.thruhere.net&gt;
</content>
</entry>
<entry>
<title>meta-gnome: add Pimlico (contacts, dates, tasks)</title>
<updated>2012-08-20T20:51:54+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross.burton@intel.com</email>
</author>
<published>2012-08-20T15:55:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=443481fec3855476f60ee34358887d00368e6859'/>
<id>urn:sha1:443481fec3855476f60ee34358887d00368e6859</id>
<content type='text'>
This has just been removed from oe-core and some people are still using the
applications.

Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Martin Jansa &lt;Martin.Jansa@gmail.com&gt;
</content>
</entry>
</feed>
